[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted openldap2.2 2.2.26-3 (i386 source)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun,  3 Jul 2005 10:41:37 +0200
Source: openldap2.2
Binary: slapd ldap-utils libldap-2.2-7
Architecture: source i386
Version: 2.2.26-3
Distribution: unstable
Urgency: low
Maintainer: Torsten Landschoff <torsten@debian.org>
Changed-By: Torsten Landschoff <torsten@debian.org>
Description: 
 ldap-utils - OpenLDAP utilities
 libldap-2.2-7 - OpenLDAP libraries
 slapd      - OpenLDAP server (slapd)
Changes: 
 openldap2.2 (2.2.26-3) unstable; urgency=low
 .
   * [SECURITY] Applied the patch available at
       http://bugzilla.padl.com/show_bug.cgi?id=210
     to force libldap to really use TLS when requested in /etc/ldap/ldap.conf
     (cf. CAN-2005-2069). Clients still will use libldap2 from openldap2
     source package so this is only to prepare unleashing the libraries of
     OpenLDAP 2.2 for unstable...
Files: 
 a50a6661ad4baa8a82c6bac898ceae05 1002 net optional openldap2.2_2.2.26-3.dsc
 481ebf221bf0e645aac8d94b13688ab4 495134 net optional openldap2.2_2.2.26-3.diff.gz
 d0dba0543ea2e8004f5fac1d13a4848c 937082 net optional slapd_2.2.26-3_i386.deb
 79e3a19c2bcfb25a7818ad3f38044345 119360 net optional ldap-utils_2.2.26-3_i386.deb
 573c364731b83bc6a5d2a5531a3142dd 152048 libs important libldap-2.2-7_2.2.26-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCx6dhdQgHtVUb5EcRAtLXAJ9Oso73BPa5nxQ4abfJ+1+YSOf+GwCeKS2d
DP7vtySTV9Ws21+HL2ksijk=
=HUZ/
-----END PGP SIGNATURE-----


Accepted:
ldap-utils_2.2.26-3_i386.deb
  to pool/main/o/openldap2.2/ldap-utils_2.2.26-3_i386.deb
libldap-2.2-7_2.2.26-3_i386.deb
  to pool/main/o/openldap2.2/libldap-2.2-7_2.2.26-3_i386.deb
openldap2.2_2.2.26-3.diff.gz
  to pool/main/o/openldap2.2/openldap2.2_2.2.26-3.diff.gz
openldap2.2_2.2.26-3.dsc
  to pool/main/o/openldap2.2/openldap2.2_2.2.26-3.dsc
slapd_2.2.26-3_i386.deb
  to pool/main/o/openldap2.2/slapd_2.2.26-3_i386.deb



Reply to: