How to keep using an old CIFS device
Ever since NTLM support was removed from the kernel <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c> last year, I've been unable to access my network scanner. It's quite old (~ 2012), but it has a huge scan area and I have a colour-calibrated workflow for it, and there's no way I could afford a suitable replacement. Curiously, for something so old, it supports AirScan, so I could resort to that, only the colour calibration is off and it needs my computer's full attention to pull scans over the network as they happen. I know no-one here has a crystal ball about where projects are going, but I'm getting a little worried that the only other way to access the scanner is via smbclient and the following options in my smb.conf: client min protocol = CORE client use spnego = no ntlm auth = ntlmv1-permitted Every time I access the share, I get the dire warning that 'The "client use spnego" option is deprecated'. The documentation has even more dire warnings about these features being removed entirely. Are there other ways to access a CIFS share? I thought there might be a fuse driver, but I can't find one. I really don't want to have to trash perfectly good hardware that's never shared outside my local LAN. thanks, Stewart
Could you connect a RasPI or something else to the system, and use a more modern protocol to talk to the real world? I have an old laser printer that does not have Wifi nor Ethernet and I put a tiny DLink router (it's abandoned, have 32MB of RAM but it's enough for OpenWRT) and I use that as a printer server. You probably can do the same with your scanner. Mauro https://www.maurosouza.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Thu, Dec 8, 2022 at 9:45 PM Stewart Russell via talk <talk@gtalug.org> wrote:
Ever since NTLM support was removed from the kernel <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c> last year, I've been unable to access my network scanner. It's quite old (~ 2012), but it has a huge scan area and I have a colour-calibrated workflow for it, and there's no way I could afford a suitable replacement. Curiously, for something so old, it supports AirScan, so I could resort to that, only the colour calibration is off and it needs my computer's full attention to pull scans over the network as they happen.
I know no-one here has a crystal ball about where projects are going, but I'm getting a little worried that the only other way to access the scanner is via smbclient and the following options in my smb.conf:
client min protocol = CORE client use spnego = no ntlm auth = ntlmv1-permitted
Every time I access the share, I get the dire warning that 'The "client use spnego" option is deprecated'. The documentation has even more dire warnings about these features being removed entirely.
Are there other ways to access a CIFS share? I thought there might be a fuse driver, but I can't find one. I really don't want to have to trash perfectly good hardware that's never shared outside my local LAN.
thanks, Stewart --- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
On Thu, Dec 08, 2022 at 07:44:46PM -0500, Stewart Russell via talk wrote:
Ever since NTLM support was removed from the kernel <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c> last year, I've been unable to access my network scanner. It's quite old (~ 2012), but it has a huge scan area and I have a colour-calibrated workflow for it, and there's no way I could afford a suitable replacement. Curiously, for something so old, it supports AirScan, so I could resort to that, only the colour calibration is off and it needs my computer's full attention to pull scans over the network as they happen.
I know no-one here has a crystal ball about where projects are going, but I'm getting a little worried that the only other way to access the scanner is via smbclient and the following options in my smb.conf:
client min protocol = CORE client use spnego = no ntlm auth = ntlmv1-permitted
Every time I access the share, I get the dire warning that 'The "client use spnego" option is deprecated'. The documentation has even more dire warnings about these features being removed entirely.
Are there other ways to access a CIFS share? I thought there might be a fuse driver, but I can't find one. I really don't want to have to trash perfectly good hardware that's never shared outside my local LAN.
Is smbclient an option? It's like an ftp client except for cifs. Should mean not mounting or worrying about what the kernel thinks. Not sure if it is willing to connect to old things that the kernel no longer supports, but worth a try if it is only for an occational transfer. -- Len Sorensen
On 09/12/2022 13.12, Lennart Sorensen wrote:
Is smbclient an option? It's like an ftp client except for cifs.
That's what I have to use. But it warns me that the (required) 'client use spnego = no' option is deprecated. So I have an undefined amount of time before this device is a paperweight, and am looking for options. Stewart
Have you written to the Samba team? When asked in 2018, Andrew said:
No change is required, yes is now the enforced default.
Andrew Bartlett
That may mean that samba 48 deprecated the bare request "use spnego" and now requires a = yes or no --dave On 12/10/22 00:29, Stewart C. Russell via talk wrote:
On 09/12/2022 13.12, Lennart Sorensen wrote:
Is smbclient an option? It's like an ftp client except for cifs.
That's what I have to use. But it warns me that the (required) 'client use spnego = no' option is deprecated. So I have an undefined amount of time before this device is a paperweight, and am looking for options.
Stewart
--- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
On 2022-12-08 19:44, Stewart Russell via talk wrote:
Ever since NTLM support was removed from the kernel
I'm surprised to hear that a driver was removed from the kernel. If you get the source for the removed module you could compile it and have it available as a loadable module for your system. -- Cheers! Kevin. http://www.ve3syb.ca/ | "Nerds make the shiny things that https://www.patreon.com/KevinCozens | distract the mouth-breathers, and | that's why we're powerful" Owner of Elecraft K2 #2172 | #include <disclaimer/favourite> | --Chris Hardwick
participants (6)
-
David Collier-Brown -
Kevin Cozens -
Lennart Sorensen -
Mauro Souza -
Stewart C. Russell -
Stewart Russell