From rmeggins at redhat.com Tue Apr 3 17:44:03 2007 From: rmeggins at redhat.com (Richard Megginson) Date: Tue, 03 Apr 2007 11:44:03 -0600 Subject: [Fedora-directory-devel] slapi extednded match plugin: How to limit attribute's to match on? In-Reply-To: <1175307040.20887.84.camel@localhost.localdomain> References: <1175307040.20887.84.camel@localhost.localdomain> Message-ID: <46129263.7060301@redhat.com> Andrew Bartlett wrote: > I've got my bitwise match plugin to load and run, but now I have an > issue. it appears that my matching rule needs to limit what attributes > it applies itself to. > > That is, when I step though to code, from this query: > > [abartlet at piglett source]$ bin/ldbsearch -H > ldapi:///data/samba/samba4/svn/source/st/dc/ldap/ldapi -b > "dc=samba,dc=example,dc=com" -s sub > '(|(&(!(groupType:1.2.840.113556.1.4.803:=1))(groupType:1.2.840.113556.1.4.803:=2147483648)(groupType:1.2.840.113556.1.4.804:=10)))' sAMAccountName groupType > # returned 0 records > > I seem to be walking all the attributes, not just the attributes in the > search expression: > > 75 errno = 0; > 76 a = strtoull((*vals)->bv_val, NULL, 10); > 77 if (errno == ERANGE) { > 78 ber_bvecfree( vals ); > 79 vals = NULL; > 80 continue; > 81 } > > (gdb) p (*vals)->bv_val > $5 = 0x8411038 "(targetattr = \"*\") (version 3.0;acl \"full access to > all by all\";allow (all)(userdn = \"ldap:///anyone\");)\n" > > The collation plugin is again to opaque for me to quite get how I'm > meant to handle this... > Well, if it makes you feel any better, after looking at the mr server code, I don't understand it either :-) This is what's really puzzling - the interface for the mr match function is this: typedef int (*mrFilterMatchFn) (void* filter, Slapi_Entry*, Slapi_Attr* vals); void *filter is a mr plugin private object (set with slapi_pblock_set (pb, SLAPI_PLUGIN_OBJECT, (void *)obj)) entry is the entry to be tested to see if this entry matches the extensible search filter. You would assume attr is the attribute from the search filter - but you would be wrong. Attr is really just e->e_attrs - the attribute list from entry, beginning with the first attribute in the list. The attribute type in question is not passed in either, which means the mr match function must somehow know which attribute type to look for. The collation plugin handles this by using or_filter_t as the obj - one of the fields is or_type, the attribute type. It also doesn't pass in the value from the filter ava, so the match fn has to keep track of that also. So it looks like the workaround is to do something similar in the bitwise code - create a structure to use for the match function callback. It looks like the type and value don't have to be a copy - they are pointers into the pblock of the search operation which has a lifetime of well after the match fn is used. The new code is attached. It looks like the better solution would be to change the code in test_extensible_filter() to pass in the type and value into the match function - it seems stupid for the plugin to have to keep track of that, but perhaps I'm missing something. -------------- next part -------------- A non-text attachment was scrubbed... Name: bitwise.c Type: text/x-csrc Size: 7052 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3245 bytes Desc: S/MIME Cryptographic Signature URL: From gfidente at babel.it Tue Apr 3 18:05:23 2007 From: gfidente at babel.it (Giulio Fidente) Date: Tue, 03 Apr 2007 20:05:23 +0200 Subject: [Fedora-directory-devel] new uid/gid autogeneration feature Message-ID: <46129763.8070109@babel.it> Hi all, someone knows how to get more informations about the new feature mentioned in the subject and how use it? there are nightly builts ready or something else for use the feature? thank you so much ! -- Giulio Fidente Babel S.r.l. - http://www.babel.it Tel. +39.06.97849121 - fax +39.06.91612446 P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma) From rmeggins at redhat.com Tue Apr 3 18:18:31 2007 From: rmeggins at redhat.com (Richard Megginson) Date: Tue, 03 Apr 2007 12:18:31 -0600 Subject: [Fedora-directory-devel] new uid/gid autogeneration feature In-Reply-To: <46129763.8070109@babel.it> References: <46129763.8070109@babel.it> Message-ID: <46129A77.1000708@redhat.com> Giulio Fidente wrote: > Hi all, > > someone knows how to get more informations about the new feature > mentioned in the subject and how use it? I'm not sure, except for the actual code. > > there are nightly builts ready or something else for use the feature? If you are using Fedora 5, 6, or 7/devel, you can yum install fedora-ds-base to use it. Otherwise, you'll have to build it from source. > > thank you so much ! -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3245 bytes Desc: S/MIME Cryptographic Signature URL: From prowley at redhat.com Tue Apr 3 20:43:11 2007 From: prowley at redhat.com (Pete Rowley) Date: Tue, 03 Apr 2007 13:43:11 -0700 Subject: [Fedora-directory-devel] new uid/gid autogeneration feature In-Reply-To: <46129763.8070109@babel.it> References: <46129763.8070109@babel.it> Message-ID: <4612BC5F.7000509@redhat.com> Giulio Fidente wrote: > Hi all, > > someone knows how to get more informations about the new feature > mentioned in the subject and how use it? > > there are nightly builts ready or something else for use the feature? > > thank you so much ! You'll need a plugin configuration entry: # plugin configuration entry dn: cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config objectclass: top objectclass: nsSlapdPlugin objectclass: extensibleObject objectclass: nsContainer cn: Distributed Numeric Assignment Plugin nsslapd-plugininitfunc: dna_init nsslapd-plugintype: preoperation nsslapd-pluginenabled: on nsslapd-plugindescription: Distributed Numeric Assignment plugin nsslapd-pluginvendor: Fedora Project nsslapd-pluginVersion: 1.1 nsslapd-pluginId: distributed-numeric-assignment nsslapd-pluginPath: /home/prowley/srv/lib/fedora-ds/plugins/libdna-plugin.so modify the last attribute to point to the directory the plugin is in on your system. some sample configuration for posix: # add plugin configuration for posix users dn: cn=Posix,cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config objectclass: top objectclass: nsContainer objectclass: extensibleObject cn: Posix dn: cn=Accounts,cn=Posix,cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config objectclass: top objectclass: extensibleObject cn: Accounts dnaType: uidNumber dnaNextValue: 500 dnaInterval: 4 dnaMagicRegen: 499 dnaFilter: (objectclass=posixAccount) # add plugin configuration for posix groups dn: cn=Groups,cn=Posix,cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config objectclass: top objectclass: extensibleObject cn: Groups dnaType: gidNumber dnaNextValue: 500 dnaInterval: 4 dnaMagicRegen: 499 dnaFilter: (objectclass=posixGroup) dnaInterval should be set to (at minimum) the number of masters you have. The original checkin post with more information: https://www.redhat.com/archives/fedora-directory-devel/2007-January/msg00007.html -- Pete -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3241 bytes Desc: S/MIME Cryptographic Signature URL: From nkinder at redhat.com Tue Apr 3 22:35:25 2007 From: nkinder at redhat.com (Nathan Kinder) Date: Tue, 03 Apr 2007 15:35:25 -0700 Subject: [Fedora-directory-devel] Please Review: (235143) Default nsslapd-saslpath setting is incorrect on non-Linux platforms Message-ID: <4612D6AD.4080005@redhat.com> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235143 Resolves: bug 235143 Bug Description: When you create a new instance on a non-Linux platform, the nsslapd-saslpath setting in dse.ldif is incorrect. It is currently set to /sasl2, but the sasl plugins are actually installed in //sasl2. This causes the server to not load any of it's SASL plugins, so it doesn't advertise any mechanisms other than EXTERNAL. Reviewed by: ??? Files: ldapserver/ldap/admin/src/create_instance.c Branch: HEAD Fix Description: The fix is just changing the default setting for the nsslapd-saslpath parameter during instance creation. Platforms tested: HP-UX 11.23, Solaris 9 Flag Day: no Doc impact: no Diffs: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=151628 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3241 bytes Desc: S/MIME Cryptographic Signature URL: From abartlet at samba.org Wed Apr 4 03:06:26 2007 From: abartlet at samba.org (Andrew Bartlett) Date: Wed, 04 Apr 2007 13:06:26 +1000 Subject: [Fedora-directory-devel] slapi extednded match plugin: How to limit attribute's to match on? In-Reply-To: <46129263.7060301@redhat.com> References: <1175307040.20887.84.camel@localhost.localdomain> <46129263.7060301@redhat.com> Message-ID: <1175655986.17106.139.camel@localhost.localdomain> On Tue, 2007-04-03 at 11:44 -0600, Richard Megginson wrote: > Andrew Bartlett wrote: > > I've got my bitwise match plugin to load and run, but now I have an > > issue. it appears that my matching rule needs to limit what attributes > > it applies itself to. > > > > That is, when I step though to code, from this query: > > > > [abartlet at piglett source]$ bin/ldbsearch -H > > ldapi:///data/samba/samba4/svn/source/st/dc/ldap/ldapi -b > > "dc=samba,dc=example,dc=com" -s sub > > '(|(&(!(groupType:1.2.840.113556.1.4.803:=1))(groupType:1.2.840.113556.1.4.803:=2147483648)(groupType:1.2.840.113556.1.4.804:=10)))' sAMAccountName groupType > > # returned 0 records > > > > I seem to be walking all the attributes, not just the attributes in the > > search expression: > > > > 75 errno = 0; > > 76 a = strtoull((*vals)->bv_val, NULL, 10); > > 77 if (errno == ERANGE) { > > 78 ber_bvecfree( vals ); > > 79 vals = NULL; > > 80 continue; > > 81 } > > > > (gdb) p (*vals)->bv_val > > $5 = 0x8411038 "(targetattr = \"*\") (version 3.0;acl \"full access to > > all by all\";allow (all)(userdn = \"ldap:///anyone\");)\n" > > > > The collation plugin is again to opaque for me to quite get how I'm > > meant to handle this... > > > Well, if it makes you feel any better, after looking at the mr server > code, I don't understand it either :-) :-) > This is what's really puzzling - the interface for the mr match function > is this: > typedef int (*mrFilterMatchFn) (void* filter, Slapi_Entry*, Slapi_Attr* > vals); > void *filter is a mr plugin private object (set with slapi_pblock_set > (pb, SLAPI_PLUGIN_OBJECT, (void *)obj)) > entry is the entry to be tested to see if this entry matches the > extensible search filter. You would assume attr is the attribute from > the search filter - but you would be wrong. Attr is really just > e->e_attrs - the attribute list from entry, beginning with the first > attribute in the list. The attribute type in question is not passed in > either, which means the mr match function must somehow know which > attribute type to look for. The collation plugin handles this by using > or_filter_t as the obj - one of the fields is or_type, the attribute > type. It also doesn't pass in the value from the filter ava, so the > match fn has to keep track of that also. > > So it looks like the workaround is to do something similar in the > bitwise code - create a structure to use for the match function > callback. It looks like the type and value don't have to be a copy - > they are pointers into the pblock of the search operation which has a > lifetime of well after the match fn is used. The new code is attached. > > It looks like the better solution would be to change the code in > test_extensible_filter() to pass in the type and value into the match > function - it seems stupid for the plugin to have to keep track of that, > but perhaps I'm missing something. Yeah, i think the current interface sucks. But it's great to have this working, and we now pass that portion of our tests. So, the next blocker is needing something I can use for USN support. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From gfidente at babel.it Thu Apr 5 09:26:09 2007 From: gfidente at babel.it (Giulio Fidente) Date: Thu, 05 Apr 2007 11:26:09 +0200 Subject: [Fedora-directory-devel] new uid/gid autogeneration feature In-Reply-To: <4612BC5F.7000509@redhat.com> References: <46129763.8070109@babel.it> <4612BC5F.7000509@redhat.com> Message-ID: <4614C0B1.9090601@babel.it> Pete Rowley wrote: > Giulio Fidente wrote: >> Hi all, >> >> someone knows how to get more informations about the new feature >> mentioned in the subject and how use it? >> >> there are nightly builts ready or something else for use the feature? >> >> thank you so much ! > > You'll need a plugin configuration entry: > [...] I will try, thank you so much! -- Giulio Fidente Babel S.r.l. - http://www.babel.it Tel. +39.06.97849121 - fax +39.06.91612446 P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma) From ed.mann at arctechnologies.net Fri Apr 6 00:18:16 2007 From: ed.mann at arctechnologies.net (Edward Mann) Date: Thu, 05 Apr 2007 19:18:16 -0500 Subject: [Fedora-directory-devel] Admin Console Message-ID: <1175818696.3619.1.camel@roadrunner.arctechnologies.net> I was in IRC asking about the Admin console, and was directed to post a message here. My questions are, 1. is anyone working on it? 2. is there a wish/ToDo list for the application. I would like to offer some time to developing the application. Thanks. -- Edward Mann ARC Technologies 1914 W. Richwoods Blvd. Peoria, IL 61604 309.645.3553 www.arctechnologies.net From rmeggins at redhat.com Mon Apr 9 15:39:01 2007 From: rmeggins at redhat.com (Richard Megginson) Date: Mon, 09 Apr 2007 09:39:01 -0600 Subject: [Fedora-directory-devel] Admin Console In-Reply-To: <1175818696.3619.1.camel@roadrunner.arctechnologies.net> References: <1175818696.3619.1.camel@roadrunner.arctechnologies.net> Message-ID: <461A5E15.4000304@redhat.com> Edward Mann wrote: > I was in IRC asking about the Admin console, and was directed to post a > message here. > > My questions are, > > 1. is anyone working on it? > No at the present time, although we are schedule to do some work on this in the very near future. > 2. is there a wish/ToDo list for the application. > Sort of - http://directory.fedoraproject.org/wiki/Wishlist - but this is very incomplete. > I would like to offer some time to developing the application. > Great! One urgent area is with gcj - we need to be able to use gcj to run the console as opposed to a proprietary jvm like sun or ibm. Another area is with sorting - it would be really nice to be able to sort the list of users in the Directory tab by different attributes. > Thanks. > > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3245 bytes Desc: S/MIME Cryptographic Signature URL: From rmeggins at redhat.com Mon Apr 9 22:14:42 2007 From: rmeggins at redhat.com (Richard Megginson) Date: Mon, 09 Apr 2007 16:14:42 -0600 Subject: [Fedora-directory-devel] Please review: Bug 235743: small memory leaks in task code Message-ID: <461ABAD2.2050809@redhat.com> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235743 Resolves: bug 235743 Bug Description: small memory leaks in task code Reviewed by: ??? Files: see diff Branch: HEAD Fix Description: There were a few places that were using slapi_get_first/next_backend without freeing the iterator cookie. Platforms tested: RHEL4 Flag Day: no Doc impact: no https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152068&action=diff From nkinder at redhat.com Mon Apr 16 20:23:56 2007 From: nkinder at redhat.com (Nathan Kinder) Date: Mon, 16 Apr 2007 13:23:56 -0700 Subject: [Fedora-directory-devel] Please Review: (236612) Default filesystem layout should follow FHS optional package standards Message-ID: <4623DB5C.6040204@redhat.com> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236612 Resolves: bug 236612 Bug Description: The current default filesystem layout of a Fedora Directory Server build is to lump everything FHS style underneath a prefix of /opt/fedora-ds. We should change this to follow the FHS standards for an optional software package, namely using /etc/opt and /var/opt. We will leave the "--with-fhs" configure option for using the /usr, /etc/, and /var layout that are used when packaging Fedora Directory Server for inclusion in Fedora Extras. Reviewed by: ??? Files: see diff Branch: HEAD Fix Description: The attached diffs implement this new default layout. In addition to using /var/opt and /etc/opt, I merged all of the component and server libraries into a single /opt/fedora-ds/lib directory. I also made the instance directories live in /opt/fedora-ds/slapd- instead of using the lib directory. Platforms tested: HP-UX 11.23 Flag Day: no Doc impact: no https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152711 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3241 bytes Desc: S/MIME Cryptographic Signature URL: From abartlet at samba.org Mon Apr 16 22:31:26 2007 From: abartlet at samba.org (Andrew Bartlett) Date: Tue, 17 Apr 2007 08:31:26 +1000 Subject: [Fedora-directory-devel] Please Review: (236612) Default filesystem layout should follow FHS optional package standards In-Reply-To: <4623DB5C.6040204@redhat.com> References: <4623DB5C.6040204@redhat.com> Message-ID: <1176762686.4096.3.camel@localhost.localdomain> On Mon, 2007-04-16 at 13:23 -0700, Nathan Kinder wrote: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236612 > Resolves: bug 236612 > Bug Description: The current default filesystem layout of a Fedora > Directory Server > build is to lump everything FHS style underneath a prefix of > /opt/fedora-ds. We > should change this to follow the FHS standards for an optional > software package, > namely using /etc/opt and /var/opt. Will you retain an option to install fedora DS under one single prefix, or will it now always scatter itself around the filesystem? Keeping a single prefix (samba uses /usr/local/samba as the default) is very useful for testing and development... Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From nkinder at redhat.com Mon Apr 16 22:53:30 2007 From: nkinder at redhat.com (Nathan Kinder) Date: Mon, 16 Apr 2007 15:53:30 -0700 Subject: [Fedora-directory-devel] Please Review: (236612) Default filesystem layout should follow FHS optional package standards In-Reply-To: <1176762686.4096.3.camel@localhost.localdomain> References: <4623DB5C.6040204@redhat.com> <1176762686.4096.3.camel@localhost.localdomain> Message-ID: <4623FE6A.3090601@redhat.com> Andrew Bartlett wrote: > On Mon, 2007-04-16 at 13:23 -0700, Nathan Kinder wrote: > >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236612 >> Resolves: bug 236612 >> Bug Description: The current default filesystem layout of a Fedora >> Directory Server >> build is to lump everything FHS style underneath a prefix of >> /opt/fedora-ds. We >> should change this to follow the FHS standards for an optional >> software package, >> namely using /etc/opt and /var/opt. >> > > Will you retain an option to install fedora DS under one single prefix, > or will it now always scatter itself around the filesystem? > > Keeping a single prefix (samba uses /usr/local/samba as the default) is > very useful for testing and development... > I spoke with Rich about this earlier. I'm going to make the above possible if a prefix is explicitly set during configure time. -NGK > Andrew Bartlett > > ------------------------------------------------------------------------ > > -- > Fedora-directory-devel mailing list > Fedora-directory-devel at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-devel > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3241 bytes Desc: S/MIME Cryptographic Signature URL: From nhosoi at redhat.com Mon Apr 16 23:00:04 2007 From: nhosoi at redhat.com (Noriko Hosoi) Date: Mon, 16 Apr 2007 16:00:04 -0700 Subject: [Fedora-directory-devel] Please Review: (236612) Default filesystem layout should follow FHS optional package standards In-Reply-To: <4623FE6A.3090601@redhat.com> References: <4623DB5C.6040204@redhat.com> <1176762686.4096.3.camel@localhost.localdomain> <4623FE6A.3090601@redhat.com> Message-ID: <4623FFF4.6040606@redhat.com> Nathan Kinder wrote: > Andrew Bartlett wrote: > >> On Mon, 2007-04-16 at 13:23 -0700, Nathan Kinder wrote: >> >> >>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236612 >>> Resolves: bug 236612 >>> Bug Description: The current default filesystem layout of a Fedora >>> Directory Server >>> build is to lump everything FHS style underneath a prefix of >>> /opt/fedora-ds. We >>> should change this to follow the FHS standards for an optional >>> software package, >>> namely using /etc/opt and /var/opt. >>> >> >> >> Will you retain an option to install fedora DS under one single prefix, >> or will it now always scatter itself around the filesystem? >> >> Keeping a single prefix (samba uses /usr/local/samba as the default) is >> very useful for testing and development... >> > > I spoke with Rich about this earlier. I'm going to make the above > possible if a prefix is explicitly set during configure time. I was about to check "review.comment#1+nhosoi". Are we having another review? ;) --noriko > > -NGK > >> Andrew Bartlett >> >> ------------------------------------------------------------------------ >> >> -- >> Fedora-directory-devel mailing list >> Fedora-directory-devel at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-devel >> > > >------------------------------------------------------------------------ > >-- >Fedora-directory-devel mailing list >Fedora-directory-devel at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-devel > > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From nkinder at redhat.com Tue Apr 17 22:54:43 2007 From: nkinder at redhat.com (Nathan Kinder) Date: Tue, 17 Apr 2007 15:54:43 -0700 Subject: [Fedora-directory-devel] Take 2 - Please Review: (236612) Default filesystem layout should follow FHS optional package standards In-Reply-To: <4623DB5C.6040204@redhat.com> References: <4623DB5C.6040204@redhat.com> Message-ID: <46255033.6010509@redhat.com> After some feedback from Rich and Andrew, I've modified my fix. I've made the default build store everything under the prefix, including the sysconfdir and localstatedir. The --with-fhs option retains it's old behavior of using /usr, /etc, and /var. A new --with-fhs-opt configure option will use the prefix (default is /opt/fedora-ds) for everything other that the sysconfdir and localstatedir. These two paths will be /etc/opt and /var/opt. New diffs are available at https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152861&action=diff -NGK Nathan Kinder wrote: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236612 > Resolves: bug 236612 > Bug Description: The current default filesystem layout of a Fedora > Directory Server > build is to lump everything FHS style underneath a prefix of > /opt/fedora-ds. We > should change this to follow the FHS standards for an optional > software package, > namely using /etc/opt and /var/opt. > > We will leave the "--with-fhs" configure option for using the /usr, > /etc/, and > /var layout that are used when packaging Fedora Directory Server for > inclusion > in Fedora Extras. > Reviewed by: ??? > Files: see diff > Branch: HEAD > Fix Description: The attached diffs implement this new default > layout. In addition > to using /var/opt and /etc/opt, I merged all of the component and > server libraries > into a single /opt/fedora-ds/lib directory. I also made the instance > directories > live in /opt/fedora-ds/slapd- instead of using the lib > directory. > Platforms tested: HP-UX 11.23 > Flag Day: no > Doc impact: no > https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152711 > ------------------------------------------------------------------------ > > -- > Fedora-directory-devel mailing list > Fedora-directory-devel at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-devel > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3241 bytes Desc: S/MIME Cryptographic Signature URL: From abartlet at samba.org Tue Apr 17 23:54:00 2007 From: abartlet at samba.org (Andrew Bartlett) Date: Wed, 18 Apr 2007 09:54:00 +1000 Subject: [Fedora-directory-devel] Re: [Fedora-directory-commits] windowsautoenroll LICENSE.txt, NONE, 1.1 aep.nsi, 1.3, 1.4 In-Reply-To: <200704171446.l3HEkGOW016959@cvs-int.fedora.redhat.com> References: <200704171446.l3HEkGOW016959@cvs-int.fedora.redhat.com> Message-ID: <1176854040.8970.55.camel@localhost.localdomain> On Tue, 2007-04-17 at 10:46 -0400, Steven W Parkinson wrote: > Author: sparkins > > Update of /cvs/dirsec/windowsautoenroll > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16941 > > Modified Files: > aep.nsi > Added Files: > LICENSE.txt > Log Message: > Add Gnu GPL license to distribution This seems to be missing the preamble, and you should be specific as to versions, when you reference the 'Gnu General Public License'. It is also traditional to put this in a file marked COPYING. (The FSF also doesn't like their document being pulled apart). > --- NEW FILE LICENSE.txt --- > Auto Enrollment Proxy License Terms > > > This software, "Auto Enrollment Proxy" is distributed > under the Gnu General Public License. The terms of the > license are reproduced below. > > > GNU GENERAL PUBLIC LICENSE > TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION > > 0. This License applies to any program or other work which contains > a notice placed by the copyright holder saying it may be distributed > under the terms of this General Public License. The "Program", below, > refers to any such program or work, and a "work based on the Program" > means either the Program or any derivative work under copyright law: > that is to say, a work containing the Program or a portion of it, > either verbatim or with modifications and/or translated into another > language. (Hereinafter, translation is included without limitation in > the term "modification".) Each licensee is addressed as "you". > > Activities other than copying, distribution and modification are not > covered by this License; they are outside its scope. The act of > running the Program is not restricted, and the output from the Program > is covered only if its contents constitute a work based on the > Program (independent of having been made by running the Program). > Whether that is true depends on what the Program does. > > 1. You may copy and distribute verbatim copies of the Program's > source code as you receive it, in any medium, provided that you > conspicuously and appropriately publish on each copy an appropriate > copyright notice and disclaimer of warranty; keep intact all the > notices that refer to this License and to the absence of any warranty; > and give any other recipients of the Program a copy of this License > along with the Program. > > You may charge a fee for the physical act of transferring a copy, and > you may at your option offer warranty protection in exchange for a fee. > > 2. You may modify your copy or copies of the Program or any portion > of it, thus forming a work based on the Program, and copy and > distribute such modifications or work under the terms of Section 1 > above, provided that you also meet all of these conditions: > > a) You must cause the modified files to carry prominent notices > stating that you changed the files and the date of any change. > > b) You must cause any work that you distribute or publish, that in > whole or in part contains or is derived from the Program or any > part thereof, to be licensed as a whole at no charge to all third > parties under the terms of this License. > > c) If the modified program normally reads commands interactively > when run, you must cause it, when started running for such > interactive use in the most ordinary way, to print or display an > announcement including an appropriate copyright notice and a > notice that there is no warranty (or else, saying that you provide > a warranty) and that users may redistribute the program under > these conditions, and telling the user how to view a copy of this > License. (Exception: if the Program itself is interactive but > does not normally print such an announcement, your work based on > the Program is not required to print an announcement.) > > These requirements apply to the modified work as a whole. If > identifiable sections of that work are not derived from the Program, > and can be reasonably considered independent and separate works in > themselves, then this License, and its terms, do not apply to those > sections when you distribute them as separate works. But when you > distribute the same sections as part of a whole which is a work based > on the Program, the distribution of the whole must be on the terms of > this License, whose permissions for other licensees extend to the > entire whole, and thus to each and every part regardless of who wrote it. > > Thus, it is not the intent of this section to claim rights or contest > your rights to work written entirely by you; rather, the intent is to > exercise the right to control the distribution of derivative or > collective works based on the Program. > > In addition, mere aggregation of another work not based on the Program > with the Program (or with a work based on the Program) on a volume of > a storage or distribution medium does not bring the other work under > the scope of this License. > > 3. You may copy and distribute the Program (or a work based on it, > under Section 2) in object code or executable form under the terms of > Sections 1 and 2 above provided that you also do one of the following: > > a) Accompany it with the complete corresponding machine-readable > source code, which must be distributed under the terms of Sections > 1 and 2 above on a medium customarily used for software interchange; or, > > b) Accompany it with a written offer, valid for at least three > years, to give any third party, for a charge no more than your > cost of physically performing source distribution, a complete > machine-readable copy of the corresponding source code, to be > distributed under the terms of Sections 1 and 2 above on a medium > customarily used for software interchange; or, > > c) Accompany it with the information you received as to the offer > to distribute corresponding source code. (This alternative is > allowed only for noncommercial distribution and only if you > received the program in object code or executable form with such > an offer, in accord with Subsection b above.) > > The source code for a work means the preferred form of the work for > making modifications to it. For an executable work, complete source > code means all the source code for all modules it contains, plus any > associated interface definition files, plus the scripts used to > control compilation and installation of the executable. However, as a > special exception, the source code distributed need not include > anything that is normally distributed (in either source or binary > form) with the major components (compiler, kernel, and so on) of the > operating system on which the executable runs, unless that component > itself accompanies the executable. > > If distribution of executable or object code is made by offering > access to copy from a designated place, then offering equivalent > access to copy the source code from the same place counts as > distribution of the source code, even though third parties are not > compelled to copy the source along with the object code. > > 4. You may not copy, modify, sublicense, or distribute the Program > except as expressly provided under this License. Any attempt > otherwise to copy, modify, sublicense or distribute the Program is > void, and will automatically terminate your rights under this License. > However, parties who have received copies, or rights, from you under > this License will not have their licenses terminated so long as such > parties remain in full compliance. > > 5. You are not required to accept this License, since you have not > signed it. However, nothing else grants you permission to modify or > distribute the Program or its derivative works. These actions are > prohibited by law if you do not accept this License. Therefore, by > modifying or distributing the Program (or any work based on the > Program), you indicate your acceptance of this License to do so, and > all its terms and conditions for copying, distributing or modifying > the Program or works based on it. > > 6. Each time you redistribute the Program (or any work based on the > Program), the recipient automatically receives a license from the > original licensor to copy, distribute or modify the Program subject to > these terms and conditions. You may not impose any further > restrictions on the recipients' exercise of the rights granted herein. > You are not responsible for enforcing compliance by third parties to > this License. > > 7. If, as a consequence of a court judgment or allegation of patent > infringement or for any other reason (not limited to patent issues), > conditions are imposed on you (whether by court order, agreement or > otherwise) that contradict the conditions of this License, they do not > excuse you from the conditions of this License. If you cannot > distribute so as to satisfy simultaneously your obligations under this > License and any other pertinent obligations, then as a consequence you > may not distribute the Program at all. For example, if a patent > license would not permit royalty-free redistribution of the Program by > all those who receive copies directly or indirectly through you, then > the only way you could satisfy both it and this License would be to > refrain entirely from distribution of the Program. > > If any portion of this section is held invalid or unenforceable under > any particular circumstance, the balance of the section is intended to > apply and the section as a whole is intended to apply in other > circumstances. > > It is not the purpose of this section to induce you to infringe any > patents or other property right claims or to contest validity of any > such claims; this section has the sole purpose of protecting the > integrity of the free software distribution system, which is > implemented by public license practices. Many people have made > generous contributions to the wide range of software distributed > through that system in reliance on consistent application of that > system; it is up to the author/donor to decide if he or she is willing > to distribute software through any other system and a licensee cannot > impose that choice. > > This section is intended to make thoroughly clear what is believed to > be a consequence of the rest of this License. > > 8. If the distribution and/or use of the Program is restricted in > certain countries either by patents or by copyrighted interfaces, the > original copyright holder who places the Program under this License > may add an explicit geographical distribution limitation excluding > those countries, so that distribution is permitted only in or among > countries not thus excluded. In such case, this License incorporates > the limitation as if written in the body of this License. > > 9. The Free Software Foundation may publish revised and/or new versions > of the General Public License from time to time. Such new versions will > be similar in spirit to the present version, but may differ in detail to > address new problems or concerns. > > Each version is given a distinguishing version number. If the Program > specifies a version number of this License which applies to it and "any > later version", you have the option of following the terms and conditions > either of that version or of any later version published by the Free > Software Foundation. If the Program does not specify a version number of > this License, you may choose any version ever published by the Free Software > Foundation. > > 10. If you wish to incorporate parts of the Program into other free > programs whose distribution conditions are different, write to the author > to ask for permission. For software which is copyrighted by the Free > Software Foundation, write to the Free Software Foundation; we sometimes > make exceptions for this. Our decision will be guided by the two goals > of preserving the free status of all derivatives of our free software and > of promoting the sharing and reuse of software generally. > > NO WARRANTY > > 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY > FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN > OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES > PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED > OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF > MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS > TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE > PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, > REPAIR OR CORRECTION. > > 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING > WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR > REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, > INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING > OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED > TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY > YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER > PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE > POSSIBILITY OF SUCH DAMAGES. > > END OF TERMS AND CONDITIONS > > > Index: aep.nsi > =================================================================== > RCS file: /cvs/dirsec/windowsautoenroll/aep.nsi,v > retrieving revision 1.3 > retrieving revision 1.4 > diff -u -r1.3 -r1.4 > --- aep.nsi 17 Apr 2007 14:33:15 -0000 1.3 > +++ aep.nsi 17 Apr 2007 14:46:14 -0000 1.4 > @@ -36,6 +36,7 @@ > dotnetpresent: > > > +file /oname=$INSTDIR\LICENSE.txt "LICENSE.txt" > file /oname=$INSTDIR\rhcsproxy.exe "proxy\${BUILDTYPE}\rhcsproxy.exe" > file /oname=$INSTDIR\messages.dll "proxy\${BUILDTYPE}\messages.dll" > file /oname=$INSTDIR\submitrequest.exe "submitrequest\${BUILDTYPE}\submitrequest.exe" > > -- > Fedora-directory-commits mailing list > Fedora-directory-commits at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-commits > -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From nhosoi at redhat.com Thu Apr 19 01:00:08 2007 From: nhosoi at redhat.com (Noriko Hosoi) Date: Wed, 18 Apr 2007 18:00:08 -0700 Subject: [Fedora-directory-devel] Please review: [Bug 237040] New: Remove obsolete makefiles In-Reply-To: References: Message-ID: <4626BF18.5090803@redhat.com> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237040 Summary: Remove obsolete makefiles Product: Fedora Directory Server Version: 1.0.4 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: medium Component: Unknown AssignedTo: nhosoi at redhat.com ReportedBy: nhosoi at redhat.com QAContact: ohegarty at redhat.com Estimated Hours: 0.0 Description of problem: Since we have completed migrating to autoconf/automake, we don't need the obsolete makefiles. ------- Additional Comments From nhosoi at redhat.com 2007-04-18 20:51 EST ------- Created an attachment (id=152974) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=152974&action=view) Obsolete makefile list to be removed Thanks, --noriko -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From ed.mann at arctechnologies.net Fri Apr 20 02:50:41 2007 From: ed.mann at arctechnologies.net (Edward Mann) Date: Thu, 19 Apr 2007 21:50:41 -0500 Subject: [Fedora-directory-devel] Admin Console Message-ID: <1177037441.3657.12.camel@roadrunner.arctechnologies.net> I would like to extend the console to be more friendly with Unix admins. My ideas. When you create a new user, you can also check a box that will auto create the users autofs entry, unless there is a better way to do this. Make the UID/GID optional. Maybe a checkbox to enable the field for manual editing? The reason for this is i read that the server can handle this now. When you add a new user, you can also add them to NetGroups that you have defined. A specific interface for adding NetGroups and others. I have not looked into anything else but adding NetGroups at the moment. Maybe an option during setup to enable NetGroups and autofs. So the admin can just get in and start adding objects. Those are the ideas that i have right now. I would like some feedback. Also is gcj really that urgent now that Sun has O.S Java? Thanks. -- Edward Mann ARC Technologies 1914 W. Richwoods Blvd. Peoria, IL 61604 309.645.3553 www.arctechnologies.net From zorox78 at gmail.com Sun Apr 22 10:01:32 2007 From: zorox78 at gmail.com (mesut sahin) Date: Sun, 22 Apr 2007 13:01:32 +0300 Subject: [Fedora-directory-devel] mysql-client Message-ID: I am using fedora core 5 when I tried to instal vpopmail it gives error that mysql.h cannot find how can I install all packages of mysqlclient. -------------- next part -------------- An HTML attachment was scrubbed... URL: From abartlet at samba.org Fri Apr 27 07:25:39 2007 From: abartlet at samba.org (Andrew Bartlett) Date: Fri, 27 Apr 2007 09:25:39 +0200 Subject: [Fedora-directory-devel] Admin Console In-Reply-To: <1177037441.3657.12.camel@roadrunner.arctechnologies.net> References: <1177037441.3657.12.camel@roadrunner.arctechnologies.net> Message-ID: <1177658739.4091.6.camel@localhost.localdomain> On Thu, 2007-04-19 at 21:50 -0500, Edward Mann wrote: > I would like to extend the console to be more friendly with Unix admins. > Also is gcj really that urgent now that Sun has O.S Java? As I understand it... It isn't Open Source yet, just promised. It's more a process being done, than a 'dump code over the wall on the announcement date'. Because of timeframes, it won't be in Fedora 7 (even after it is open sourced it will take time to integrate into Fedora). Aside from 'it would be the right thing to do', the gcj requirement is about 'a package in Fedora must not depend on things not in Fedora', which still holds. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From abartlet at samba.org Fri Apr 27 15:24:16 2007 From: abartlet at samba.org (Andrew Bartlett) Date: Fri, 27 Apr 2007 17:24:16 +0200 Subject: [Fedora-directory-devel] [PATCH] Allow replication in 00core.ldif Message-ID: <1177687456.10493.45.camel@localhost.localdomain> I've been playing with Fedora DS replication and Samba, and have been making good progress. See http://wiki.samba.org/index.php/Samba4/LDAP_Backend/Fedora_DS for the evolving set of instructions (should get better over the next week). I need this patch applied (and possibly the bitwise patch too) to get the replication working. I also had to hack up mmr.pl to take a port, and not assume 389 Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. http://redhat.com -------------- next part -------------- A non-text attachment was scrubbed... Name: updated-schema-for-replication.patch Type: text/x-patch Size: 6668 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mmr.pl Type: application/x-perl Size: 13624 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From nhosoi at redhat.com Sat Apr 28 00:14:46 2007 From: nhosoi at redhat.com (Noriko Hosoi) Date: Fri, 27 Apr 2007 17:14:46 -0700 Subject: [Fedora-directory-devel] Commit: [Bug 237356] Move DS Admin Code into Admin Server In-Reply-To: <200704272219.l3RMJTv1022148@bugzilla.redhat.com> References: <200704272219.l3RMJTv1022148@bugzilla.redhat.com> Message-ID: <463291F6.7070107@redhat.com> Summary: Move DS Admin Code into Admin Server https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237356 If you are on the fedora-directory-commits mailing list, sorry about the lots of commit messages that filled your INBOX. They are all for removing or moving out the unused code from the Fedora DS base package. Thanks, --noriko ------- Additional Comments From nhosoi at redhat.com 2007-04-27 17:55 EST ------- Created an attachment (id=153667) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153667&action=view) cvs commit message (Comment #2) ------- Additional Comments From nhosoi at redhat.com 2007-04-27 18:19 EST ------- Created an attachment (id=153668) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153668&action=view) cvs commit message (Comment #3) ------- Additional Comments From nhosoi at redhat.com 2007-04-27 19:01 EST ------- Created an attachment (id=153674) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153674&action=view) cvs commit message (Comment #4, #6) ------- Additional Comments From nhosoi at redhat.com 2007-04-27 19:19 EST ------- Created an attachment (id=153675) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153675&action=view) cvs commit message (Comment #5) ------- Additional Comments From nhosoi at redhat.com 2007-04-27 19:41 EST ------- Created an attachment (id=153677) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153677&action=view) cvs commit message (Comment #8) ------- Additional Comments From nhosoi at redhat.com 2007-04-27 19:49 EST ------- Created an attachment (id=153678) --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=153678&action=view) cvs commit message (Comment #8, #9) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: