mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Radoslaw Szkodzinski (AstralStorm) <lkml@astralstorm.puszkin.org>
To: "Steve French" <smfrench@gmail.com>
Cc: "Jeff Layton" <jlayton@redhat.com>,
	"Adrian Bunk" <bunk@kernel.org>,
	"Guenter Kukkukk" <linux@kukkukk.com>,
	samba-technical@lists.samba.org, linux-kernel@vger.kernel.org,
	sfrench@samba.org
Subject: Re: [2.6 patch] remove smbfs
Date: Thu, 31 Jan 2008 09:26:40 +0100	[thread overview]
Message-ID: <20080131092640.5bc79dbd@astralstorm.puszkin.org> (raw)
In-Reply-To: <524f69650801301730m42abca6dn76d21fbdddbe89b5@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

On Wed, 30 Jan 2008 19:30:55 -0600
"Steve French" <smfrench@gmail.com> wrote:

> On Jan 30, 2008 7:13 PM, Jeff Layton <jlayton@redhat.com> wrote:
> > On Thu, 31 Jan 2008 02:47:17 +0200
> > > > > > > In addition, cifs cannot completely replace smbfs atm.
> > > > > > > Even todays sold NAS-boxes (often running anchient
> > > > > > > samba-2.x.x) work only with smbfs on the client side.
> I am not convinced that this (mounting to older servers) would be a
> problem with the proper mount options but it is more intuitive for
> smbfs for some of the lanman servers.   I do want to make sure that we
> don't make it too easy to mount with insecure lanman (ie due to
> downgrade attacks) without the user at least doing that (specify weak
> lanman security explicitly).  Today the user has to explicitly specify
> sec=lanman which is confusing but at least makes explicit the weaker
> security.
> 
> There are four common issues with mounting to these very old servers:
> 1) remembering to mount specifying lanman security (sec=lanman)

I think it'd be nice to add an alias called oldsmb or similar for that
option in mount.cifs. It should only be needed for old win9x servers.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-31  8:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 22:08 Adrian Bunk
2008-01-28 22:55 ` Steve French
2008-01-30 18:27 ` Jan Engelhardt
2008-01-30 18:53   ` Steve French
2008-01-30 19:05     ` Jan Engelhardt
2008-01-31  1:23       ` Steve French
2008-01-31 11:18         ` Jan Engelhardt
2008-01-31  2:03       ` David Newall
2008-01-31  2:23         ` Jan Engelhardt
2008-01-31  2:54           ` Steve French
2008-01-30 20:52     ` Guenter Kukkukk
2008-01-30 21:16 ` Guenter Kukkukk
2008-01-30 22:41   ` Jeff Layton
2008-01-30 22:58     ` Adrian Bunk
2008-01-31  0:34       ` Jeff Layton
2008-01-31  0:47         ` Adrian Bunk
2008-01-31  1:13           ` Jeff Layton
2008-01-31  1:30             ` Steve French
2008-01-31  8:26               ` Radoslaw Szkodzinski [this message]
2008-01-31  9:51               ` Andi Kleen
2008-01-31  1:34           ` Steve Langasek
2008-01-31  2:58             ` Steve French
2008-01-31  0:58     ` Lennart Sorensen
2008-02-05  8:18     ` Andrew Morton
2008-02-05 11:31       ` Jeff Layton
2008-02-05 18:17         ` Andrew Morton
2008-02-05 14:04       ` Alejandro Riveira Fernández
2008-02-05 14:58       ` 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:
  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=20080131092640.5bc79dbd@astralstorm.puszkin.org \
    --to=lkml@astralstorm.puszkin.org \
    --cc=bunk@kernel.org \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@kukkukk.com \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    --cc=smfrench@gmail.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

all inboxes | Powered by JetHome®