diff options
| author | Andrew Tridgell <tridge@samba.org> | 1997-09-16 04:41:16 +0000 |
|---|---|---|
| committer | Andrew Tridgell <tridge@samba.org> | 1997-09-16 04:41:16 +0000 |
| commit | 57c2578cb2b7e02acc6c04d07adc11a77c40aa9c (patch) | |
| tree | 340729e71e98ad0fe7f3bf6a4b651aaa1286c5e4 /source3/nmbsync.c | |
| parent | 72b02acd7e2c24efcff2faffb2555d70378b01b3 (diff) | |
| download | samba-57c2578cb2b7e02acc6c04d07adc11a77c40aa9c.tar.gz samba-57c2578cb2b7e02acc6c04d07adc11a77c40aa9c.tar.bz2 samba-57c2578cb2b7e02acc6c04d07adc11a77c40aa9c.zip | |
- change generate_challenge() to use md4 instead of des
- move routines about a bit between smbencrypt.c and smbdes.c. Ensure
that there is no entry point for normal DES operation
- add the following comment:
This code is NOT a complete DES implementation. It implements only
the minimum necessary for SMB authentication, as used by all SMB
products (including every copy of Microsoft Windows95 ever sold)
In particular, it can only do a unchained forward DES pass. This
means it is not possible to use this code for encryption/decryption
of data, instead it is only useful as a "hash" algorithm.
There is no entry point into this code that allows normal DES operation.
I believe this means that this code does not come under ITAR
regulations but this is NOT a legal opinion. If you are concerned
about the applicability of ITAR regulations to this code then you
should confirm it for yourself (and maybe let me know if you come
up with a different answer to the one above)
(This used to be commit 35b92e725f351c9a9f2846a6b55f71c234f187c7)
Diffstat (limited to 'source3/nmbsync.c')
0 files changed, 0 insertions, 0 deletions