From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: cifs: unable to mount cifs 1.0 shares because support for NTLM and weaker authentication algorithms was removed #forregzbot
Date: Mon, 10 Jan 2022 15:57:01 +0100 [thread overview]
Message-ID: <4f8b62ce-8d4a-9bf6-e75c-acb039ebec10@leemhuis.info> (raw)
In-Reply-To: <dce98c91-d28c-0f5a-b177-1f4275cf0f35@leemhuis.info>
On 23.12.21 11:48, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
>
> There is a regression discussed in bugzilla I'd like to see tracked, to
> ensure it's not forgotten. Quoting a few parts of the report:
>
>> After 5.15.0, I'm unable to mount a CIFS 1.0 share from a media player which I cannot update (vendor no longer provides updates).
>>
>> Original issue is logged here: https://bugs.gentoo.org/821895, with the most interesting bits probably being:
>
>> Ok, 2.5 hours of bisecting later and I can confirm that the culprit is
>>
>> [76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c] cifs: remove support for NTLM and weaker authentication algorithms
>>
>> The commit before works fine, this commit prevents me from mounting the smb shares on my mede8er 600x 3d.
>
> #regzbot introduced: 76a3c92ec9e0668e
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215375
> #regzbot link: https://bugs.gentoo.org/821895
>
> I'm not CCing any of the developers for now, looks like they are
> handling it in bugzilla.
>
> And yes, starting a extra thread for this is a hack hate myself, but I
> need some workaround for tracking due to the distributed nature of bug
> reporting with various different bug trackers in use (reminder:
> bugzilla.kernel.org is not the only one used by kernel developers).
>
> Ciao, Thorsten
>
There is a proper report now tracked by regzbot:
#regzbot dup-of:
https://lore.kernel.org/lkml/CAJjP=Bt52AW_w2sKnM=MbckPkH1hevPMJVWm_Wf%2BwThmR72YTg@mail.gmail.com/
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
prev parent reply other threads:[~2022-01-10 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 10:48 cifs: unable to mount cifs 1.0 shares because support for NTLM and weaker authentication algorithms was removed Thorsten Leemhuis
2022-01-10 14:57 ` Thorsten Leemhuis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f8b62ce-8d4a-9bf6-e75c-acb039ebec10@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).