[cifs-protocol] [REG: 111070650721347] Behavior of AllowNT4Crypto
Edgar Olougouna
edgaro at microsoft.com
Wed Jul 6 15:41:23 MDT 2011
[Adding case number]
Metze,
I am taking care of this. I have opened a document issue on MS-NRPC. I will follow-up as soon as I have news.
Regards,
Edgar
-----Original Message-----
From: Josh Curry
Sent: Tuesday, July 05, 2011 10:21 AM
To: Stefan (metze) Metzmacher; Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: RE: Behavior of AllowNT4Crypto
Hi Stefan, thank you for your question. A member of the protocol documentation team will be in touch with you soon.
Josh Curry
Escalation Engineer
469.775.7215
Exceeding your expectations is my highest priority. If you would like to provide feedback on your case you may contact my manager at allisong at microsoft.com.
-----Original Message-----
From: Stefan (metze) Metzmacher [mailto:metze at samba.org]
Sent: Tuesday, July 05, 2011 2:04 AM
To: Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: Behavior of AllowNT4Crypto
Hi,
can you please document the behavior that is triggered by the following parameter.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Netlogon\Parameters]
"AllowNT4Crypto"=dword:00000001
I can't find this in MS-NRPC.
Is there any interaction with the RequireStrongKey parameter?
Thanks!
metze
More information about the cifs-protocol
mailing list