Hello there
I have two linux boxes running samba. Both have the same workgroup. On both machines I have user 'charles' with the same smb password. However to see each other's user shares I am asked to log in. How do I make the smb server accept the 'charles' from the remote machine as the local charles? On window shares, without domains, matching username/passwords is usually the only requirement.
Cheers
Charles
On Friday 18 June 2004 23:47, Charles Garcia-Tobin wrote:
Hello there
I have two linux boxes running samba. Both have the same workgroup. On both machines I have user 'charles' with the same smb password. However to see each other's user shares I am asked to log in. How do I make the smb server accept the 'charles' from the remote machine as the local charles? On window shares, without domains, matching username/passwords is usually the only requirement.
Ahh so what you need is a smbclient version of the smbusers file to map the Unix username to the smb one on the client side...not sure such a thing exists as I always use NFS to filehshare between unix clients.
It won't "just work" between Unix hosts as the username is irrelevant, it's the UID that counts.
*********************Dirty Hack alert, DONT do this if you care about not disclosing your passwords******************************
One cheat may be to call the smbclient (or smbmount) with a -A filename option Where filename is a file containing
username = <value> password = <value> domain = <value>
You could put this in $HOME/.foo and set it so only the owner could read it, anybody that logs in and has a .foo will then be authenticated on the smb shares.
A REALLY dirty way is to set the environment variable PASSWD As if you specify nothing samba assumes $USER as the login name and $PASSWD as it's password. You may also have to add an -N to silence the password prompt.
Naturally if you do either of these then you potentially expose your credentials to anybody who happens across a terminal logged in as you. I provide this as an example of how NOT to do things :o)
Hey Wayne
Tar for the advice. Shame it don't just work. I wanted to use Samba coz of my my mixed network. It seems silly to run an extra server. However given the security of it I think I'll just stick to NFS.
Cheers
Charles
On Saturday 19 June 2004 16:50, Wayne Stallwood wrote:
On Friday 18 June 2004 23:47, Charles Garcia-Tobin wrote:
Hello there
I have two linux boxes running samba. Both have the same workgroup. On both machines I have user 'charles' with the same smb password. However to see each other's user shares I am asked to log in. How do I make the smb server accept the 'charles' from the remote machine as the local charles? On window shares, without domains, matching username/passwords is usually the only requirement.
Ahh so what you need is a smbclient version of the smbusers file to map the Unix username to the smb one on the client side...not sure such a thing exists as I always use NFS to filehshare between unix clients.
It won't "just work" between Unix hosts as the username is irrelevant, it's the UID that counts.
*********************Dirty Hack alert, DONT do this if you care about not disclosing your passwords******************************
One cheat may be to call the smbclient (or smbmount) with a -A filename option Where filename is a file containing
username = <value> password = <value> domain = <value>
You could put this in $HOME/.foo and set it so only the owner could read it, anybody that logs in and has a .foo will then be authenticated on the smb shares.
A REALLY dirty way is to set the environment variable PASSWD As if you specify nothing samba assumes $USER as the login name and $PASSWD as it's password. You may also have to add an -N to silence the password prompt.
Naturally if you do either of these then you potentially expose your credentials to anybody who happens across a terminal logged in as you. I provide this as an example of how NOT to do things :o)
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!