[389-users] Announcing 389 Directory Server version 1.3.2.24

2014-10-17 Thread Noriko Hosoi
389 Directory Server 1.3.2.24 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.2.24. Fedora packages are available from the Fedora 20 repository. The new packages and versions are: * 389-ds-base-1.3.2.24-1 A source tarball is available for download at Download

[389-users] Announcing 389 Directory Server version 1.3.3.5

2014-10-17 Thread Noriko Hosoi
389 Directory Server 1.3.3.5 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.3.5. Fedora packages are available from the Fedora 21 and Rawhide repositories. The new packages and versions are: * 389-ds-base-1.3.3.5-1 A source tarball is available for download

Re: [389-users] Regarding patch availability for RHBA-2014:1623-1

2014-10-17 Thread Rich Megginson
On 10/17/2014 07:58 AM, Balaji P wrote: Hi While analyzing this problem we noticed this issue is released for RHEL in version 1.2.11.15 version. Is it possible to deliver the fix in 1.2.8.2 The 389 team is not going to do this. and 1.2.11.32 streams? There isn't a 1.2.11.32 "stream". Th

[389-users] custom object classes and attributes

2014-10-17 Thread Chase Miller
Hello, So I have a development ldap server up and running with all of my custom object classes and attributes. Now, is there a way to export these and import them on my new production boxes, so I don't have to re-create all of them. Chase -- 389 users mailing list 389-users@lists.fedoraproject.o

[389-users] Regarding patch availability for RHBA-2014:1623-1

2014-10-17 Thread Balaji P
Hi While analyzing this problem we noticed this issue is released for RHEL in version 1.2.11.15 version. Is it possible to deliver the fix in 1.2.8.2 and 1.2.11.32 streams? (or) Is there any patch available for this fix? Bug Fix Advisory - RHBA-2014:1623-1 ---

Re: [389-users] How relevant is Poodlebleed Bug to 389?

2014-10-17 Thread Rich Megginson
On 10/17/2014 02:55 AM, Paul Tobias wrote: You probably want to disable SSLv3 on the admin server too. Add the following line to /etc/dirsrv/admin-serv/console.conf: NSSProtocol TLSv1.0,TLSv1.1 Documentation here: https://git.fedorahosted.org/cgit/mod_nss.git/plain/docs/mod_nss.html Regarding

Re: [389-users] How relevant is Poodlebleed Bug to 389?

2014-10-17 Thread Paul Tobias
You probably want to disable SSLv3 on the admin server too. Add the following line to /etc/dirsrv/admin-serv/console.conf: NSSProtocol TLSv1.0,TLSv1.1 Documentation here: https://git.fedorahosted.org/cgit/mod_nss.git/plain/docs/mod_nss.html Regarding the directory server, I didn't find "nsTLS1"