Re: NTLM session security
"Christopher R. Hertel" <[email protected]>
| Newsgroups | gmane.network.samba.java |
|---|---|
| Organization | ubiqx Development, uninq. |
| Message-ID | <[email protected]> |
For a better understanding of NTLMSSP, NTLMv2 Session Security, and CIFS signing, I recommend the following... http://davenport.sourceforge.net/ntlm.html https://blogs.msdn.com/b/openspecification/archive/2010/04/20/ntlm-keys-and-sundry-stuff.aspx https://blogs.msdn.com/b/openspecification/archive/2010/11/15/ntlm-terminology-ms-nlmp-vs-http-davenport-sourceforge-net-ntlm-html.aspx http://msdn.microsoft.com/en-us/library/cc236621.aspx You might also have a look at the authentication section of http://ubiqx.org/cifs/ Whch should provide the base understanding necessary to interpret the rest of those docs. Chris -)----- Michael B Allen wrote: > On Mon, Oct 10, 2011 at 11:43 PM, Mohan Radhakrishnan <[email protected]> wrote: >> Hi, >> >> I might have understand this wrongly. Does this mean all data >> passing through the socket using JCIFS is signed and verified at the >> other end ? > > If signatures are negotiated then yes. > > But if you are looking for "NTLMv2 session security" like you might > use with the Windows NTLMSSP, CIFS does not use that. CIFS implements > it's own message signatures that are not even based on streams. Each > CIFS message has a designated area for a signature. It only uses the > encryption key negotiated during NTLMv2 authentication. > > Mike > -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- [email protected] OnLineBook -- http://ubiqx.org/cifs/ -)----- [email protected]