Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 580000 - net-fs/samba-4.2.11 connecting to shares: ntlmssp_handle_neg_flags: Got challenge flags[0x60898205] - possible downgrade detected!
Summary: net-fs/samba-4.2.11 connecting to shares: ntlmssp_handle_neg_flags: Got chall...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo's SAMBA Team
URL: https://bugzilla.samba.org/show_bug.c...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-14 20:53 UTC by Erik Quaeghebeur
Modified: 2016-09-08 12:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Quaeghebeur 2016-04-14 20:53:45 UTC
With the upgrade to samba-4.2.11, I cannot access some shares using smbclient or kio-based access.

The error I get using smbclient is

ntlmssp_handle_neg_flags: Got challenge flags[0x60898205] - possible downgrade detected! missing_flags[0x00000010] - NT code 0x80090302
  NTLMSSP_NEGOTIATE_SIGN
SPNEGO(ntlmssp) login failed: NT code 0x80090302
session setup failed: NT code 0x80090302

When downgrading to 4.2.9, things work nicely.

I can use 4.2.9 as a workaround, but an important question in that case is whether the vulnerabilities fixed in the 4.2.11 release also affect clients (I don't use samba's server component).
Comment 1 Alex Xu (Hello71) 2016-04-19 16:26:14 UTC
five bucks says your server is misconfigured
Comment 2 Erik Quaeghebeur 2016-04-19 21:21:08 UTC
(In reply to Alex Xu (Hello71) from comment #1)
> five bucks says your server is misconfigured

My institute's server being misconfigured is a possibility. Should I pass the error message also to them or wait for a reaction from the samba team? This is mostly a Microsoft shop and they will most likely not do much effort to support my Linux system, so my first communication to them should be as precise and to the point as possible.
Comment 3 Erik Quaeghebeur 2016-07-30 20:27:32 UTC
It seems 4.2.9 has now been removed from the tree. While I am keeping my installed version for now, this does make testing new versions for me difficult, as I cannot then return to a previous, known-good version. Is it possible to re-add 4.2.9 to the tree, please?
Comment 4 bugs.gentoo.org 2016-09-08 07:54:41 UTC
(In reply to Erik Quaeghebeur from comment #3)
> possible to re-add 4.2.9 to the tree, please?
You can add it into local overlay.

In the changelog for Samba 4.2.12 fixed:
ВUG 11849: auth/ntlmssp: Add ntlmssp_{client,server}:force_old_spnego option for testing.
ВUG 11850: NetAPP SMB servers don't negotiate NTLMSSP_SIGN.
Comment 5 Erik Quaeghebeur 2016-09-08 08:29:14 UTC
(In reply to bugs.gentoo.org from comment #4)
>
> You can add it into local overlay.

How? (It is now only installed on my system, I don't have the ebuild anymore.)

> ВUG 11850: NetAPP SMB servers don't negotiate NTLMSSP_SIGN.

https://bugzilla.samba.org/show_bug.cgi?id=11850 does indeed seem the upstream version. (I was 4 days earlier here!)

Alex Xu (Hello71), you owe me $5! (If you were in any way serious about this: please donate it to Samba: https://www.samba.org/samba/donations.html.)

Once I know how to preserve 4.2.9, I'll test 4.2.14 and I guess after that, successful, this can be marked as FIXED UPSTREAM or so. Perhaps this is would be reason enough to stabilize 4.2.14 then.
Comment 6 Erik Quaeghebeur 2016-09-08 11:47:42 UTC
> (In reply to bugs.gentoo.org from comment #4)
> >
> > You can add it into local overlay.
> 
> How? (It is now only installed on my system, I don't have the ebuild
> anymore.)

OK, I've learnt about quickpkg.
Comment 7 Erik Quaeghebeur 2016-09-08 12:32:45 UTC
(In reply to Erik Quaeghebeur from comment #5)
>
> I'll test 4.2.14 and I guess after that,
> if successful, this can be marked as FIXED UPSTREAM or so. Perhaps this is
> would be reason enough to stabilize 4.2.14 then.

Ok, tested. It's fixed with 4.2.14. I'll mark as RESOLVED UPSTREAM. The package maintainers will know best when to mark as stable.