samba without user authentication? can this be done? only based on machine
Oliver
world. without the need for any user authentication.
I dont mind if there is a way to authenticate just by the machine, even that
would do.
Brian K. White
"Oliver" <os...@pulsemining.com.au> wrote in message
news:mssx7.30$Yt1....@nsw.nnrp.telstra.net...
mkdir /usr/share/mp3
chown nobody:nobody /usr/share/mp3
cat >>/usr/local/etc/smb.conf <<%%
[mp3]
path = /usr/share/mp3
read only = No
guest ok = Yes
%%
cd /usr/local/etc/rc.d
./samba.sh stop
./samba.sh start
I just did this and it's working. Except I used swat to make the changes to
the smb.conf file, and either it automatically restarts samba when
necessary, or this change does not require a restart, because I didn't use
swat to restart samba manually. So maybe you don't need the last three
lines, but they dont' hurt.
I do get a password prompt when I first click on my new "mp3" share on the
bsd box in network neighborhood (actually my network places, since I'm using
win2k) but I just hit "cancel" without filling anything in and I am now
copying my mp3 directory tree from my win2k box to my bsd box without a
password or a user name. In real life, the files are being created owned by
user nobody (the default samba guest account), and I don't have write
permission anywhere but /usr/share/mp3 and below.
--
Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
Brian K. White
"Brian K. White" <br...@aljex.com> wrote in message
news:U5Dx7.1446$s9.1...@news1.rdc1.nj.home.com...
god dammit!!!
I'm sorry, I thought this question was asked in the freebsd newsgroup, and
this is a freebsd answer.
in the above answer, I do not know the paths for the samba components on
osr5
the answer is the same, but the exact paths are different on sco
/usr/local/etc/smb.conf is probably /etc/smb.conf
/usr/local/etc/rc.d/samba.sh is probably something like /etc/rc2.d/S??samba
Perhaps I should have just given the answer in terms of what to click on in
swat, that would have been the same on both os's and most others too. Except
swat is never enabled by default and then I'd have to describe enabling and
using swat before even touching on the real question.
Tony Lawrence
You can do it without any password at all if you set
[public]
comment = Public Stuff
path = /public
public = yes
writable = yes
--
Tony Lawrence
SCO/Linux Support Tips, How-To's, Tests and more: http://pcunix.com
Nenio
[homes]
comment = Home Directories
browseable = no
writable = yes
guest ok = yes <--- This is the parameter
"Oliver" <os...@pulsemining.com.au> escreveu na mensagem
news:mssx7.30$Yt1....@nsw.nnrp.telstra.net...
Bill Vermillion
Brian K. White <br...@aljex.com> wrote:
>%%
>cd /usr/local/etc/rc.d
>./samba.sh stop
>./samba.sh start
>I just did this and it's working. Except I used swat to make the changes to
>the smb.conf file, and either it automatically restarts samba when
>necessary, or this change does not require a restart, because I didn't use
>swat to restart samba manually. So maybe you don't need the last three
>lines, but they dont' hurt.
A reading of the man page would have answered that question.
--------------------------
The swat status page tries to connect with smbd and
nmbd at the address 127.0.0.1 to determine if they
are running. Not adding 127.0.0.1 will cause smbd
and nmbd to always show "not running" even if they
really are. This can prevent swat from start-
ing/stopping/restarting smbd and nmbd.
--------------------------
Man pages keep you from guessing.
--
Bill Vermillion - bv @ wjv . com
Brian K. White
"Tony Lawrence" <to...@pcunix.com> wrote in message
news:3BC729CE...@pcunix.com...
Ah cool. This is better. Thanks Tony.
Didn't see any options like this in swat... Just looked again to be sure,
even with the "advanced view"
This is samba version pre-3.0.0 (cvs as of a week or two ago)
Guess swat isn't all it's cracked up to be, or this is syntax that has
changed recently.
Just verified this does work as advertised in this version. No password
prompt, no need to hit "cancel", just instant access.
Also verified that you do not need to stop and start anything when you add a
share in the config file. I edited my smb.conf and without doing anything
else, immediately went to "my network places" and the new share was there.
Brian K. White
"Bill Vermillion" <bi...@wjv.com> wrote in message news:GL3y6...@wjv.com...
two problems with this.
1) I do not have 127.0.0.1 or anything else listed in any of the "allow" or
"deny" fields, and the status page starts, stops, and tracks the current
state fine. (ok perhaps 127.0.0.1 is assumed in certain places if you never
set anything at all)
2) I have since determined that no restarting is even necessary at least for
some changes. I added a share manually (no swat, just vi) to the smb.conf
and the share immediately showed up in network neighborhood (the next time I
opened or refreshed it)
--
Brian K. White -- br...@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani
>
Bill Vermillion
Well if you are running TCP/IP you had better have 127.0.0.1
Try this "ping localhost" and tell me what address you see.
>2) I have since determined that no restarting is even necessary at
>least for some changes. I added a share manually (no swat, just
>vi) to the smb.conf and the share immediately showed up in network
>neighborhood (the next time I opened or refreshed it)
>> Man pages keep you from guessing.
As is said previously 'man pages keep you from guessing'. :-)
==============
The configuration file, and any files that it includes,
are automatically reloaded every minute, if they change.
You can force a reload by sending a SIGHUP to the server.
Reloading the configuration file will not affect connec-
tions to any service that is already established. Either
the user will have to disconnect from the service, or smbd
killed and restarted.
==============
Tony Lawrence
> > You can do it without any password at all if you set
> >
> > [public]
> > comment = Public Stuff
> > path = /public
> > public = yes
> > writable = yes
>
> Ah cool. This is better. Thanks Tony.
> Didn't see any options like this in swat... Just looked again to be sure,
> even with the "advanced view"
> This is samba version pre-3.0.0 (cvs as of a week or two ago)
> Guess swat isn't all it's cracked up to be, or this is syntax that has
> changed recently.
I cheat: http://pcunix.com/Books/sambaor.html
Really indespensable if you have Samba stuff.
Brian K. White
well sure it's in my hosts file, but the above piece of text doesn't say
where it's talking about, so I assumed it was talking about smb.conf, since
that's what we were talking about. I can see what it means now though.
Simon Hobson
(in message <UmOx7.3029$s9.6...@news1.rdc1.nj.home.com>):
> Also verified that you do not need to stop and start anything when you add a
> share in the config file. I edited my smb.conf and without doing anything
> else, immediately went to "my network places" and the new share was there.
I beieve that Samba reads the config file each time a client connects, which
means you can do things that vary at runtime (such as run multiple servers
with different names).
So changes you make to smb.conf should automatically apply to all new
connections - though I would think that some global config options may not be
acted on without a restart.
Simon
Bill Vermillion
Brian K. White <br...@aljex.com> wrote:
>
>"Bill Vermillion" <bi...@wjv.com> wrote in message
>news:GL4vs...@wjv.com...
>> In article <IuOx7.3038$s9.6...@news1.rdc1.nj.home.com>,
>> Brian K. White <br...@aljex.com> wrote:
>> >
>> >"Bill Vermillion" <bi...@wjv.com> wrote in message
>news:GL3y6...@wjv.com...
>> >> In article <U5Dx7.1446$s9.1...@news1.rdc1.nj.home.com>,
>> >> Brian K. White <br...@aljex.com> wrote:
>> >>
>> Well if you are running TCP/IP you had better have 127.0.0.1
>> Try this "ping localhost" and tell me what address you see.
>well sure it's in my hosts file, but the above piece of text
>doesn't say where it's talking about, so I assumed it was talking
>about smb.conf, since that's what we were talking about. I can see
>what it means now though.
What I was trying to get across is that without 127.0.0.1 nothing
will work.