From: Jens Knoell <jens@surefoot.com>
To: eatley@wowcorp.com
Cc: linux-admin@vger.kernel.org
Subject: Re: Best way to enable 'guest' access onto Linux fileserver?
Date: Wed, 23 Mar 2005 09:15:09 -0700 [thread overview]
Message-ID: <4241960D.2010507@surefoot.com> (raw)
In-Reply-To: <008101c52f18$3cc98ed0$580aa8c0@lanadmin>
Hi Eve
Eve Atley wrote:
>Sorry if my subject is misleading. What I am hoping to do is give 'guest'
>access to our 'public' directory (home/shared/public and nothing else) for
>consultants who visit us inside the office on a case-by-case basis. This is
>to enable consultants to share files across the network when they visit.
>
>Right now, we use Samba credentials (ie. Somebody/password) on our Redhat 9
>box, and match their computer logon (Somebody/password) to that so people
>don't have to enter a special username/password to connect to our server.
>Therefore, all our employees have their own username/password combo on their
>computers, as well as their own samba username/password that matches.
>
>So say Joe comes in as a consultant, logged in as joe/computerpassword.
>Obviously, when he attempts to access our server, he recieves a prompt
>asking him for a username/password, since no joe/computerpassword exists on
>our Linux box.
>
>So how would you handle this? By creating a guest/guest account on the Linux
>box that allows access to only /home/public, then giving that info to a
>consultant on an as-needed basis? Or some other way?
>
>Thanks,
>Eve
>
>
I think this is what you're looking for:
[everyone]
comment = Public guest directory
browseable = yes
writeable = yes
path = /home/shared/public
guest ok = yes
public = yes
printable = no
force create mode = 0777
force directory mode = 0777
create mode = 0777
security mask = 0777
And in the global section:
map to guest = Bad User
Make sure the permissions for directory /home/shared/public are 0777.
This configuration literally allows everyone to connect with r/w access,
no matter what username/password they use.
J
next prev parent reply other threads:[~2005-03-23 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 10:27 how to protect against peer-to-peer? Luca Ferrari
2004-11-22 13:02 ` urgrue
2004-11-22 13:39 ` Adam Lang
2004-11-22 13:53 ` Adrian C.
2004-11-22 13:57 ` Adrian C.
2005-02-12 1:01 ` RH Ent. 3.0 = no support for firewire HD? Eve Atley
2005-03-22 19:49 ` Best way to enable 'guest' access onto Linux fileserver? Eve Atley
2005-03-22 20:09 ` Grant Coady
2005-03-23 16:15 ` Jens Knoell [this message]
2005-03-23 21:10 ` Eve Atley
2005-03-23 23:01 ` Jens Knoell
2005-03-28 16:53 ` Resolved: " Eve Atley
2004-11-22 15:53 ` how to protect against peer-to-peer? Jens Knoell
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=4241960D.2010507@surefoot.com \
--to=jens@surefoot.com \
--cc=eatley@wowcorp.com \
--cc=linux-admin@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.