archive mirror
 help / color / mirror / Atom feed
From: Davyd McColl <>
Subject: Possible regression: unable to mount CIFS 1.0 shares from older machines since 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c
Date: Mon, 10 Jan 2022 08:06:37 +0200	[thread overview]
Message-ID: <> (raw)

Good day

I'm following advice from the thread at 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
( 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.


             reply	other threads:[~2022-01-10  6:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10  6:06 Davyd McColl [this message]
2022-01-10 14:11 ` Possible regression: unable to mount CIFS 1.0 shares from older machines since 76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c Thorsten Leemhuis
2022-01-10 17:31 ` Steve French
2022-01-10 20:30   ` Davyd McColl
2022-01-10 22:13     ` Steve French
2022-01-11  6:45       ` Davyd McColl
2022-01-11 21:51         ` Steve French
2022-01-11 23:26           ` Steve French
2022-01-12  2:32         ` ronnie sahlberg
2022-01-12  5:49           ` Davyd McColl
2022-01-28 13:30             ` Thorsten Leemhuis
2022-01-28 13:39               ` Davyd McColl
2022-01-28 13:50               ` ronnie sahlberg
2022-01-28 14:02                 ` Thorsten Leemhuis
2022-01-28 14:23                   ` ronnie sahlberg
2022-02-18 13:30                   ` Davyd McColl
2022-03-02  6:58                     ` Thorsten Leemhuis
2022-03-02 17:28                       ` Davyd McColl
2022-03-03  0:50                       ` Linus Torvalds
2022-03-03  1:27                         ` Steve French
2022-03-04  6:43                           ` Thorsten Leemhuis
2022-07-27 20:04                         ` Clemens Leu
2022-07-28  2:27                           ` Steve French
     [not found] <>
2022-01-10 12:15 ` Thorsten Leemhuis
2022-01-11  3:16   ` Steve French

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 \
    --in-reply-to='' \ \ \ \

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