Re: Possible regression: unable to mount CIFS 1.0 shares from older machines since 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c

[Thorsten Leemhuis <regressions@leemhuis.info>]

Hi, this is your Linux kernel regression tracker speaking.

Top-posting for once, to make this easy accessible to everyone.

TWIMC, the parent mail quoted below misses all the important people in
To/CC. That was not the case in an earlier mail from the author that got
rejected as it was HTML. There is a reply to that mail now that made it
to the lists and everyone in the loop, hence it afaics is better to
reply there instead if you consider to send one:

https://lore.kernel.org/lkml/ff982786-4033-7450-c10c-8ce71c28d6eb@leemhuis.info/

Ciao, Thorsten

P.S.: Trying to make regzbot handle this:

#regzbot ^introduced 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c
#regzbot title cifs: unable to shares that require NTLM or weaker
authentication algorithms
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215375
#regzbot monitor:
https://lore.kernel.org/lkml/ff982786-4033-7450-c10c-8ce71c28d6eb@leemhuis.info/

On 10.01.22 07:06, Davyd McColl wrote:
> Good day
> 
> I'm following advice from the thread at
> https://bugzilla.kernel.org/show_bug.cgi?id=215375 as to how to report
> this, so please bear with me and redirect me as necessary.
> 
> Since commit 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c, I'm unable to
> mount a CIFS 1.0 share ( from a media player: mede8er med600x3d, which
> runs some older linux). Apparently I'm not the only one, according to
> that thread, though the other affected party there is windows-based.
> 
> I first logged this in the Gentoo bugtracker
> (https://bugs.gentoo.org/821895) and a reversion patch is available
> there for the time being.
> 
> I understand that some of the encryption methods upon which the
> original feature relied are to be removed and, as such, the ability to
> mount these older shares was removed. This is sure to affect anyone
> running older Windows virtual machines (or older, internally-visible
> windows hosts) in addition to anyone attempting to connect to shares
> from esoteric devices like mine.
> 
> Whilst I understand the desire to clean up code and remove dead
> branches, I'd really appreciate it if this particular feature remains
> available either by kernel configuration (which suits me fine, but is
> likely to be a hassle for anyone running a binary distribution) or via
> boot parameters. In the mean-time, I'm updating my own sync software
> to support this older device because if I can't sync media to the
> player, the device is not very useful to me.