Hello All!
I have got a $#|7load of crypto updates that I'd like to commit; they
are all over my tree, so let me describe what they do, and anyone who
wishes to review any part of them can get the appropriate bits.
1) Revisit the way libscrypt/libdescript get built. This is partially
based on
On Sat, 28 Aug 1999, Mark Murray wrote:
3) Upgade libdes. This is mainly for KerberosIV and Kerberos5. It does
not hurt anything else. This will go into src/crypto.
You might also like to turn on the x86 assembler code (it's only for
pentiums, I think, so would have to be a non-default option
On Sat, 28 Aug 1999, Mark Murray wrote:
3) Upgade libdes. This is mainly for KerberosIV and Kerberos5. It does
not hurt anything else. This will go into src/crypto.
You might also like to turn on the x86 assembler code (it's only for
pentiums, I think, so would have to be a non-default
Mark Murray wrote:
Hello All!
I have got a $#|7load of crypto updates that I'd like to commit; they
are all over my tree, so let me describe what they do, and anyone who
wishes to review any part of them can get the appropriate bits.
Something that came up recently, both for me
On Sat, 28 Aug 1999, Doug wrote:
Something that came up recently, both for me and someone else on the list
is the ability to have DES libs in the system and still use MD5 passwords
as the default. I have no idea how difficult this would be to do, but if
someone has it in mind here's
I haven't had much feedback on this code so would like to hear how well it
works for people. Unfortunately I can't correct any bugs at the moment
until I get my computer (which is at this moment being unloaded from a
plane at the airport :-) set up and back on the net, but I tested it a
fair
