Trevor Osatchuk wrote:
> Hello there.  Sharity was installed by a different sysadmin, who has since
> left us, so I don't have any experience.  I have read the web-manual and
> have tried to find the answers to these questions:
> 
> There is a directory called /CIFS that has all of the Windows computers and
> UNIX computers with Samba running in it.  Logged in as root, when I cd to a
> directory of one of the Windows boxes and do an ls I get 'permission
> denied'.  I mounted a share from my own pc, used my login and password,
> unmounted it and then was able to browse the directory.  Is this how
> browsing is supposed to work?  Is this browsing?

What you found is the effect of a workaround in Sharity. In principle, no
user should have access to server data (even the list of shares) without
providing a valid account name and password for the server. That's how CIFS
security works. If you want to browse the shares of the servers in the CIFS
directory, you must first log in to the server with 'cifslogin' from the
commandline or run the GUI which will ask for the data on demand.

'cifsmount' does a login, too, since it has to access the server. Once you
are logged in, your account name and (encrypted) password are stored in
memory.

The root account is treated specially and this is what I meant with
"workaround" in the beginning. Root must be able to access any file a user
can access since some tasks running on behalf of a user do their job with
root privileges. Sharity therefore always tries to grant access to root. If
no user is logged in, this will fail, of course. However, if a user is
already logged in, Sharity will use this account for root.

Regards, Christian.

--
Dipl.-Ing. Christian Starkjohann
Objective Development
mailto:[EMAIL PROTECTED] | http://www.obdev.at/


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
To unsubscribe send a mail with the words "unsubscribe sharity-talk" in the
body to <[EMAIL PROTECTED]>. If you want to reach a human, please write to
<[EMAIL PROTECTED]>.

Reply via email to