Skip to contentSkip to conversation

-mm merge plans for 2.6.20

DISCUSSION Chuck Ebbert 2 participants 2 messages Dec 10, 2006 – Dec 11, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <[email protected]>

Quoted 3 lines · Steve French

smbfs deprecation is ok but there are a few things to consider:

2) minor holes in backlevel server (OS/2 and Windows 9x/WindowsME) support

How well-tested is the plaintext password support?

By default the /proc/fs/cifs/SecurityFlags setting is 0x7 (MAY_SIGN | MAY_NTLM | MAYNTLMV2). Trying to connect to an old Samba server with that, I got a message that the server requested a plain text password but client support was disabled.

After changing the flags to 0x37 (adding MAY_LANMAN | MAY_PLNTXT), I got "invalid password." Looking at the ethereal traces, it seemed that the password was being sent as encrypted Unicode, and the only way to make it connect was to set the flags to 0x30.

Also, the client doesn't automatically pick up the domain name from smb.conf like smbfs does.

Signature · 2 lines
Chuck
"Even supernovas have their duller moments."
#1 lore raw
Quoted 15 lines · Chuck Ebbert

In-Reply-To: <[email protected]>

Quoted 2 lines · Steve French

smbfs deprecation is ok but there are a few things to consider:

How well-tested is the plaintext password support?

By default the /proc/fs/cifs/SecurityFlags setting is 0x7 (MAY_SIGN | MAY_NTLM | MAYNTLMV2). Trying to connect to an old Samba server with that, I got a message that the server requested a plain text password but client support was disabled.

Quoted 5 lines

After changing the flags to 0x37 (adding MAY_LANMAN | MAY_PLNTXT), I got "invalid password." Looking at the ethereal traces, it seemed that the password was being sent as encrypted Unicode, and the only way to make it connect was to set the flags to 0x30.

I don't remember any problems reported with plain text password support on current cifs and I have certainly seen it negotiated with no problem, but I will double check with your reported flag combination.

Quoted 4 lines

Also, the client doesn't automatically pick up the domain name from smb.conf like smbfs does.

That is true, and is intentional. cifs sends a domain of null (ie use the server's
default domain) - but it can be overridden on mount