From: Paulo Alcantara <pc@cjr.nz>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Tom Talpey <tom@talpey.com>, Steven French <sfrench@samba.org>,
Byron Stanoszek <gandalf@winds.org>,
Shyam Prasad N <nspmangalore@gmail.com>,
linux-cifs <linux-cifs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: CIFS regression mounting vers=1.0 NTLMSSP when hostname is too long
Date: Fri, 06 May 2022 11:05:06 -0300 [thread overview]
Message-ID: <87wneyah9p.fsf@cjr.nz> (raw)
In-Reply-To: <CAN05THQYKRChdR_4T86dGtCO=xY+cWpfa6_fOVNh9WSB=RNE-A@mail.gmail.com>
ronnie sahlberg <ronniesahlberg@gmail.com> writes:
> This regression should be easy to fix, but maybe we should not have
> done the initial change in the first place.
> If things is broken and do not work under SMB1, that is a good thing.
> Instead of adding features or fixing
> missing parts to SMB1 we should just tell people to switch to SMB2 instead.
>
> I think if things do not work correctly or things are missing in smb1,
> that is a GOOD THING.
> :-)
LOL - couldn't agree more :-)
next prev parent reply other threads:[~2022-05-06 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 20:36 CIFS regression mounting vers=1.0 NTLMSSP when hostname is too long Byron Stanoszek
2022-05-04 1:35 ` Paulo Alcantara
2022-05-04 5:43 ` Steven French
2022-05-04 19:15 ` Paulo Alcantara
2022-05-04 20:18 ` Tom Talpey
2022-05-04 20:58 ` Paulo Alcantara
2022-05-06 2:03 ` Steve French
2022-05-06 2:19 ` ronnie sahlberg
2022-05-06 14:05 ` Paulo Alcantara [this message]
2022-05-04 7:13 ` Thorsten Leemhuis
2022-05-17 20:37 ` Paulo Alcantara
2022-05-22 4:40 ` Steven French
2022-05-23 2:32 ` Byron Stanoszek
2022-05-25 3:17 ` Byron Stanoszek
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=87wneyah9p.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=gandalf@winds.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.org \
--cc=tom@talpey.com \
/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).