Date: Mon, 19 May 2003 13:29:40 -0700 From: Gordon Tetlow <gordont@gnf.org> To: sdebnath@cs.purdue.edu Cc: freebsd-current@freebsd.org Subject: Re: Acceptable LDAP solutions Message-ID: <20030519202940.GH1950@roark.gnf.org> In-Reply-To: <1053375013.3ec93a25df857@webmail.purdue.edu> References: <0E972CEE334BFE4291CD07E056C76ED8DB2DBE@bragi.housing.ufl.edu> <1053365929.3ec916a957190@webmail.purdue.edu> <20030519194508.GD1950@roark.gnf.org> <1053373287.3ec93367bbdff@webmail.purdue.edu> <20030519195949.GF1950@roark.gnf.org> <1053375013.3ec93a25df857@webmail.purdue.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--fyA1p1RlO9nWxe3v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, May 19, 2003 at 03:10:13PM -0500, Shawn Debnath wrote:
> Looks like LDAP uses plain old crypt(), and I am forced into using that b=
/c of
> the setup here. Time to make sure the LDAP server is secure at least. Th=
anks
> for your help Gordon.=20
You should at least be able to use MD5:
dn: cn=3DJoe L. User,ou=3Dpeople,dc=3Dexample,dc=3Dcom
objectClass: posixAccount
cn: Joe L. User
uid: joeluser
uidNumber: 1000
gidNumber: 1000
homeDirectory: /home/joeluser
userPassword: {MD5}<standard md5 password hash>
-gordon
--fyA1p1RlO9nWxe3v
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+yT60Ru2t9DV9ZfsRAlTjAKCbetFDSg7+r4+ASP5otb71UkiT4QCePnJ2
WGP7gPPYMhcM224RgPgKIJE=
=IzUN
-----END PGP SIGNATURE-----
--fyA1p1RlO9nWxe3v--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030519202940.GH1950>