From: Jeff Layton <jlayton@poochiereds.net>
To: Shirish S Pargaonkar <shirishp@us.ibm.com>
Cc: smfltc@linux.vnet.ibm.com, hch@infradead.org,
linux-cifs-client-bounces+shirishp=us.ibm.com@lists.samba.org,
Jeff Layton <jlayton@redhat.com>,
linux-cifs-client@lists.samba.org,
samba-technical@lists.samba.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-cifs-client] Re: [PATCH] CIFS: make sec=none force an anonymous mount
Date: Sat, 5 May 2007 08:03:03 -0400 [thread overview]
Message-ID: <20070505120258.GC5054@salusa.poochiereds.net> (raw)
In-Reply-To: <OFEFD715DD.89A7A57F-ON872572D2.003A0BCE-862572D2.003AC6CA@us.ibm.com>
On Sat, May 05, 2007 at 05:41:35AM -0500, Shirish S Pargaonkar wrote:
>
> When a session setup request is sent as an anonymous user (NUL user),
> should/could there be
> password associated with that?
> Right now, sec=none option, will prompt you for a password.
We should probably turn off password prompting if sec=none is specified.
> And when we add code to retry session setup as anonymous user if the first
> session setup request
> fails, should that retry request be sent with the password or without
> password?
>
> When smbfs sends requests as an anonymous user, it does not send a password
> along with it.
>
I'd say we'd want to avoid sending along the password in any situation where
it wasn't really needed.
-- Jeff
next prev parent reply other threads:[~2007-05-05 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070504024910.CE97B1638AF@lists.samba.org>
2007-05-04 15:26 ` Steve French (smfltc)
2007-05-04 15:57 ` Jeff Layton
2007-05-04 16:41 ` Steve French (smfltc)
[not found] ` <OFEFD715DD.89A7A57F-ON872572D2.003A0BCE-862572D2.003AC6CA@us.ibm.com>
2007-05-05 12:03 ` Jeff Layton [this message]
2007-05-05 20:47 ` [linux-cifs-client] " Steve French (smfltc)
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=20070505120258.GC5054@salusa.poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client-bounces+shirishp=us.ibm.com@lists.samba.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=shirishp@us.ibm.com \
--cc=smfltc@linux.vnet.ibm.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®