archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: "" <>
Subject: cifs: unable to mount cifs 1.0 shares because support for NTLM and weaker authentication algorithms was removed
Date: Thu, 23 Dec 2021 11:48:51 +0100	[thread overview]
Message-ID: <> (raw)

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:, 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:
#regzbot link:

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: is not the only one used by kernel developers).

Ciao, Thorsten

             reply	other threads:[~2021-12-23 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 10:48 Thorsten Leemhuis [this message]
2022-01-10 14:57 ` cifs: unable to mount cifs 1.0 shares because support for NTLM and weaker authentication algorithms was removed #forregzbot Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).