[16667] in Kerberos_V5_Development
Re: DES string-to-key and crypto modules
daemon@ATHENA.MIT.EDU (Jeffrey Altman)
Sat Mar 5 14:48:04 2011
X-Envelope-From: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: krbdev@mit.edu
Message-ID: <4D72936A.9040005@secure-endpoints.com>
Date: Sat, 05 Mar 2011 14:47:54 -0500
From: Jeffrey Altman <jaltman@secure-endpoints.com>
MIME-Version: 1.0
To: krbdev@mit.edu
In-Reply-To: <201103051904.p25J4Ppb000442@outgoing.mit.edu>
Reply-To: jaltman@secure-endpoints.com
Content-Type: multipart/mixed; boundary="===============1681477049=="
Errors-To: krbdev-bounces@mit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1681477049==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enigB540EE2432A6602665A1F224"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB540EE2432A6602665A1F224
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 3/5/2011 2:04 PM, ghudson@mit.edu wrote:
> Currently libk5crypto delegates responsibility for string-to-key to
> the modules. There are some issues with this:
>=20
> * OpenSSL implements DES_string_to_key() as some kind of ancient
> backwards-compatibility measure, but at least in the version I
> tested (1.0.0a), it did not appear to correctly handle weak
> keys--there's code for it, but it's #ifdef'd out. As a consequence,
> it produces wrong answers for two of the test vectors in RFC 3960.
> The chances of running into this case non-deliberately in operation
> are, of course, quite low.
>=20
> * I don't think NSS implements it at all. (Currently, the NSS module
> does completely the wrong thing for DES string to key, I believe;
> I'm treating that as a bug.)
>=20
> My inclination is to move the built-in DES string-to-key into
> lib/crypto/krb and stop asking the modules to do it, as it's far from
> a standard crypto primitive like PBKDF2. Does that seem reasonable?
It is quite reasonable. Please rename the function when you do so.
--------------enigB540EE2432A6602665A1F224
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
iQEcBAEBAgAGBQJNcpNsAAoJENxm1CNJffh4gSwIAIqlN5OXMbHnlkIB4f+hQgC5
oDA84WJgKmOyZWoo4JXl7mOGi3ep8z82+R2H8WCdfvQf1lCRxIPV1AhOrJaRUJf4
GZUK/E4+L2NOTyS3WO6cwSaFl+hiRwaqhB359oZEKVRCnY1UtTMtVlQZWSLicMUa
h+q4Su8H1mV7iJpf8Ds1ajOwkWoXwwXYET5jWaHADWCJ4EBwIHQDUyg2c3PmYerN
Ykp4HtEFmIaA4Ie+JG61uuzPcOBwKVeo/rEwMIBLXkkmzaD7DOkKFQN4IjgdqSxC
4nFEQEA2fNXoYIOfkHvq50rtlfNZ8A8x7LT534Swkk/j/15JIjeTmRLvxvmUWrQ=
=8px5
-----END PGP SIGNATURE-----
--------------enigB540EE2432A6602665A1F224--
--===============1681477049==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
--===============1681477049==--
