Fwd: [PATCH] cifs: Fix broken sec=ntlmv2/i sec mount option for Samba server

Shirish Pargaonkar shirishpargaonkar at gmail.com
Wed Aug 24 08:45:07 MDT 2011


On Tue, Aug 23, 2011 at 11:34 PM, Christopher R. Hertel <crh at samba.org> wrote:
> The official explanation of what actually goes in those blobs and how the
> information is handled wasn't available until roughly 2 years ago, and it's
> buried in dense verbiage.  My guess is that no one has had time nor cause to
> review NTLMv2 blob handling--which is now somewhat outdated--since the
> documentation finally became available.
>
> Note also that Microsoft uses very different terminology than we do.  I
> think most of the names we use are from the work Eric Glass did as part of
> Davenport (which is still cited as expert information).
>
> Microsoft (Obaid) has posted two blog entries, the first of which is a
> mapping from Eric's :
>
> https://blogs.msdn.com/b/openspecification/archive/2010/11/15/ntlm-terminology-ms-nlmp-vs-http-davenport-sourceforge-net-ntlm-html.aspx
> https://blogs.msdn.com/b/openspecification/archive/2010/04/20/ntlm-keys-and-sundry-stuff.aspx
>
> Jeremy Allison wrote:
>> On Tue, Aug 23, 2011 at 08:41:12PM -0500, Steve French wrote:
>>> Wonder why we had the time in that field if Samba doesn't accept it
>>> but Windows does - is this a server bug?
>>
>> Maybe - can you send a debug level 10 log when the server
>> fails to accept your blob so we can see why ?
>>
>> Thanks,
>>
>> Jeremy.
>
> --
> "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/     -)-----   crh at ubiqx.mn.org
> OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org
>

As far as I know MS-NLMP is the only document that talks about AV
pairs in details.
So in case of raw ntlmv2, where there is not exchange of negotiate, response,
authenticate messages like in ntlmssp auth mech, which document stands/states
what should be the contents of the blob, specifically which AV pairs can exist?


More information about the samba-technical mailing list