During negprot request, shouldn't cifs _always_ set the "extended security negotiation" bit in flags2 ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



some background:

cifs tried to connect to a XP box, which was joined to a domain.
smbclient (and Mac) were working - cifs not.

On that XP box GPOs (or others) were set in that way, that _only_
NTLMSSP connections were allowed at all.

During the "negotiate protocol" request, cifs does _not_ set the
"extended security negotiation" bit in flags2.
    in cifs terms: #define SMBFLG2_EXT_SEC cpu_to_le16(0x800)
Cifs supports that - but does not offer that capability to the server.

So the XP server did response to _not_ support extended security in
the capabilities field...
Cifs tried default ntlm - and failed to connect.
Any mount options regarding "sec=....." don't help here!

So shouldn't cifs _always_ set the "extended security negotiation" bit in flags2
during negprot (to get proper server caps)?

Atm one can workaround with:

echo 0x80080 > /proc/fs/cifs/SecurityFlags   or
echo 0x80    > /proc/fs/cifs/SecurityFlags

to force NTLMSSP.

Cheers, Günter
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux