Skip to contentSkip to conversation

packet signing and DFS referrals

DISCUSSION Michael 2 participants 3 messages Dec 3, 2013 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

Michael

author
#0 lore raw

Dear cifs experts,

I tried to find some more information about my issue but was unsuccesful so far. We have a mixed Microsoft/Netapp environment with a number of linux clients were DFS was recently enabled. Kerberos Single-Sign-On is broken here because of what I believe are incosistencies with packet signing requirements. The server responsible for the DFS ROOT is requiring signing:

mount -t cifs //master/share mnt -o cruid=someid,sec=krb5,...

mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

[21866613.989219] CIFS VFS: Server requires packet signing to be enabled in
/proc/fs/cifs/SecurityFlags.
[21866613.989401] CIFS VFS: cifs_mount failed w/return code = -95

So I enabled it with krb5i:

mount -t cifs //master/share mnt -o cruid=someid,sec=krb5i,...

But when accessing a dfs referral the next server has no packet signing enabled (I believe this is the netapp default).

ls mnt/share2
[...]
dmesg | tail -n 2

[21866657.445227] CIFS VFS: signing required but server lacks support
[21866657.445441] CIFS VFS: cifs_mount failed w/return code = -95

Kernel version is 3.2.39-2 and cifs-utils 5.2-1.

My questions are:

+ might this incosistency really be the problem here?
+ are deferral-based security flags supported by the protocol?
+ how to proceed? (besides fixing the environment)

kind regards,
Michael

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 34 lines · On Tue, 3 Dec 2013 10:11:00 +0000 (UTC) Michael…

Dear cifs experts,

I tried to find some more information about my issue but was unsuccesful so far. We have a mixed Microsoft/Netapp environment with a number of linux clients were DFS was recently enabled. Kerberos Single-Sign-On is broken here because of what I believe are incosistencies with packet signing requirements. The server responsible for the DFS ROOT is requiring signing:

mount -t cifs //master/share mnt -o cruid=someid,sec=krb5,...

mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

[21866613.989219] CIFS VFS: Server requires packet signing to be enabled in
/proc/fs/cifs/SecurityFlags.
[21866613.989401] CIFS VFS: cifs_mount failed w/return code = -95

So I enabled it with krb5i:

mount -t cifs //master/share mnt -o cruid=someid,sec=krb5i,...

But when accessing a dfs referral the next server has no packet signing enabled (I believe this is the netapp default).

ls mnt/share2
[...]
dmesg | tail -n 2

[21866657.445227] CIFS VFS: signing required but server lacks support
[21866657.445441] CIFS VFS: cifs_mount failed w/return code = -95

Kernel version is 3.2.39-2 and cifs-utils 5.2-1.

Quoted 9 lines

My questions are:

+ might this incosistency really be the problem here?
+ are deferral-based security flags supported by the protocol?
+ how to proceed? (besides fixing the environment)

kind regards,
Michael

Yeah, that was broken in older kernels.

There was an overhaul of the auth selection code in v3.11, so it should work correctly with current ones.

With those, just mount the first server with 'sec=krb5' and ensure that 0x1 is set in /proc/fs/cifs/SecurityFlags (it should be by default). With the current code, if the server requires signing it should be transparently enabled unless the client has explicitly disabled it.

Signature · 1 line
Jeff Layton <[email protected]>

A message that is not in the archive (sent off-list or not yet received): 20131203082937.56e1b9fe-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org

#4 lore raw
Quoted 49 lines · On Tue, 3 Dec 2013 08:29:37 -0500 Jeff Layton…
Quoted 34 lines · On Tue, 3 Dec 2013 10:11:00 +0000 (UTC) Michael…

Dear cifs experts,

I tried to find some more information about my issue but was unsuccesful so far. We have a mixed Microsoft/Netapp environment with a number of linux clients were DFS was recently enabled. Kerberos Single-Sign-On is broken here because of what I believe are incosistencies with packet signing requirements. The server responsible for the DFS ROOT is requiring signing:

mount -t cifs //master/share mnt -o cruid=someid,sec=krb5,...

mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

[21866613.989219] CIFS VFS: Server requires packet signing to be enabled in
/proc/fs/cifs/SecurityFlags.
[21866613.989401] CIFS VFS: cifs_mount failed w/return code = -95

So I enabled it with krb5i:

mount -t cifs //master/share mnt -o cruid=someid,sec=krb5i,...

But when accessing a dfs referral the next server has no packet signing enabled (I believe this is the netapp default).

ls mnt/share2
[...]
dmesg | tail -n 2

[21866657.445227] CIFS VFS: signing required but server lacks support
[21866657.445441] CIFS VFS: cifs_mount failed w/return code = -95

Kernel version is 3.2.39-2 and cifs-utils 5.2-1.

Quoted 9 lines

My questions are:

+ might this incosistency really be the problem here?
+ are deferral-based security flags supported by the protocol?
+ how to proceed? (besides fixing the environment)

kind regards,
Michael

Yeah, that was broken in older kernels.

Quoted 8 lines

There was an overhaul of the auth selection code in v3.11, so it should work correctly with current ones.

With those, just mount the first server with 'sec=krb5' and ensure that 0x1 is set in /proc/fs/cifs/SecurityFlags (it should be by default). With the current code, if the server requires signing it should be transparently enabled unless the client has explicitly disabled it.

Ahh yeah, there's also commit 0b7bc84000d71f3647ca33ab1bf5bd928535c846 that may fix the problem in a less invasive way on earlier kernels. I think that went into v3.9, but should be easy to backport to earlier ones.

Signature · 1 line
Jeff Layton <[email protected]>