On Wed, 24 Oct 2012 11:45:46 +0200
Martijn de Gouw <[email protected]> wrote:

> Setting this secFlg allows usage of dfs where some servers require
> signing and others don't.
> 
> Signed-off-by: Martijn de Gouw <[email protected]>
> ---
> :100644 100644 b39bb4a... 4da9dd3... M        fs/cifs/connect.c
>  fs/cifs/connect.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
> index b39bb4a..4da9dd3 100644
> --- a/fs/cifs/connect.c
> +++ b/fs/cifs/connect.c
> @@ -994,7 +994,7 @@ static int cifs_parse_security_flavors(char *value,
>  
>       switch (match_token(value, cifs_secflavor_tokens, args)) {
>       case Opt_sec_krb5:
> -             vol->secFlg |= CIFSSEC_MAY_KRB5;
> +             vol->secFlg |= CIFSSEC_MAY_KRB5 | CIFSSEC_MAY_SIGN;
>               break;
>       case Opt_sec_krb5i:
>               vol->secFlg |= CIFSSEC_MAY_KRB5 | CIFSSEC_MUST_SIGN;

Looks like a reasonable bandaid until someone overhauls the auth
selection code for sanity...

Reviewed-by: Jeff Layton <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to