Matthias Nagel wrote:
Hi Phil,
Probably a fairly trivial patch if you feel like it ;o)
I had a quick glace at the source code and I found two files named
smbencrypt.c. If you give me a hint, which is the correct file to start
with, I will brosw the source code from that point and see what I
On 7 Sep 2013, at 16:43, Alan DeKok al...@deployingradius.com wrote:
Matthias Nagel wrote:
Hi Phil,
Probably a fairly trivial patch if you feel like it ;o)
I had a quick glace at the source code and I found two files named
smbencrypt.c. If you give me a hint, which is the correct file to
Arran Cudbard-Bell wrote:
Can't we assume src as UTF8 for NAI (RFC4282)?
Ha, ha, ha, ha cough. 4282 is wrong. And no one implements any of it.
The MS-CHAP RFCs are silent on the subject of character encoding. The
unofficial word from Microsoft is MS-CHAP uses the local encoding.
Sorry, my mail program tricked me and used the wrong destination address.
-- Weitergeleitete Nachricht --
Betreff: Re: smbencrypt calculates false hash for German umlauts andother
non-ASCII letters
Datum: Samstag 07 September 2013, 19:13:17
Von: Matthias Nagel
Hello,
if a do a smbencrypt ä then the output for the NT hash is
B5CF5E386433C7CB69E43ED774717792 but the correct hash would be
3104EAB484D59EFABCEA2C44B07F41D3. (If you do not see the letter: It is a
small a with two dots, unicode code point 00E4.) Similar results hold for
other umlauts,
Matthias Nagel matthias.h.na...@gmail.com wrote:
Hello,
if a do a smbencrypt ä then the output for the NT hash is
B5CF5E386433C7CB69E43ED774717792 but the correct hash would be
3104EAB484D59EFABCEA2C44B07F41D3. (If you do not see the letter: It
is a small a with two dots, unicode code point
Hi Phil,
Probably a fairly trivial patch if you feel like it ;o)
I had a quick glace at the source code and I found two files named
smbencrypt.c. If you give me a hint, which is the correct file to start with,
I will brosw the source code from that point and see what I can do. But
probably not
7 matches
Mail list logo
