![](https://seccdn.libravatar.org/avatar/433921d165f58380f515550f741b0fff.jpg?s=120&d=mm&r=g)
Am 03.01.23 um 20:55 schrieb Till Dörges:
On 02.01.23 16:41, Till Dörges wrote:
On 02.01.23 05:43, Felix Miata wrote:
5.14.21-150400.24.38-default boots, but I can't use it, because OS/2 connectivity is a must. 5.14.21-150400.24.33-default solves the problem, keeps OS/2 connected. [...] mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
I also observe a regression with openSUSE Leap 15.4 (x86-64) for SMB mounts between these two kernels:
ok kernel-default-5.14.21-150400.24.33.2.x86_64 FAIL kernel-default-5.14.21-150400.24.38.1.x86_64
Failing SMB shares are configured with CIFS version 1.0. (I know, you're not supposed to use 1.0, but I'm not calling the shots on that one.)
Error reported by mount is different, though:
- Exit code 32 - Return code 20 (not a directory)
The share in question is configured with CIFS version 1.0 and security mode NTLM.
I haven't found a bugzilla entry on b.o.o.
I guess this is probably https://bugzilla.opensuse.org/show_bug.cgi?id=1206935 reported on Friday. Happens for me too, smb connection to a Win2000 VM, 5.14.21-150400.24.38-default is broken, 5.14.21-150400.24.33-default works.
Upstream apparently has gotten rid of NTLM already:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i...
Also this upstream bug seems to be related:
https://bugzilla.kernel.org/show_bug.cgi?id=215375
According to
rpm -q --changelog kernel-default-5.14.21-150400.24.38.1.x86_64
it seems as if that particular commit is not part of the RPM.
But it looks like some other commit was added/backported to 5.14.21-150400.24.38.1 that accidentally disables 1.0 and/or NTLM?
While I'm all in favor of removing cryptographically weak protocols it shouldn't be done w/o some sort of announcement/warning because I'm guessing that there are quite a few devices which only offer services via 1.0 and/or NTLM.
Regards -- Till