linux-kernel - Re: [PATCH] cifs: connect: added option krb5mi which may allow package signing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 26 Feb 2014 12:26:34 -0800
From:	Jeff Layton <jlayton@...ba.org>
To:	"Lorenz Bucher" <Lorenz.Bucher@....de>
Cc:	sfrench@...ba.org, linux-cifs@...r.kernel.org,
	samba-technical@...ts.samba.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cifs: connect: added option krb5mi which may allow
 package signing

On Wed, 26 Feb 2014 14:46:47 +0100
"Lorenz Bucher" <Lorenz.Bucher@....de> wrote:

> Solves an issue with dfs where servers using package signing are
> mixed with servers which don't use package signing.
> 
> Signed-off-by: Lorenz Bucher <lorenz.bucher@....de>
> ---
>  fs/cifs/connect.c |    3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
> index 56c152d..9d06dd8 100644
> --- a/fs/cifs/connect.c
> +++ b/fs/cifs/connect.c
> @@ -1104,6 +1104,9 @@ cifs_parse_mount_options(const char *mountdata, const char *devname,
>                         if (!value || !*value) {
>                                 cERROR(1, "no security value specified");
>                                 continue;
> +                       } else if (strnicmp(value, "krb5mi", 6) == 0) {
> +                               vol->secFlg |= CIFSSEC_MAY_KRB5 | 
> +                                       CIFSSEC_MAY_SIGN;
>                         } else if (strnicmp(value, "krb5i", 5) == 0) {
>                                 vol->secFlg |= CIFSSEC_MAY_KRB5 |
>                                         CIFSSEC_MUST_SIGN;

This looks like it applies to a really old kernel. I think that problem
was what commit 0b7bc84000d71f3647ca33ab1bf5bd928535c846 was intended
to fix.

-- 
Jeff Layton <jlayton@...ba.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/