On 04/20/10 10:52 AM, lattera wrote:
I tried this example out and I saw my uid finally go across the wire.
What example did you try and how did you try it? How do I get my UID
to go across the wire?
ls -la /net/server/share
which actually can be thought of as:
1) mount server:/share onto /net/server/share
2) ls -ls /net/server/share
And the "mount" part goes across as root. It isn't the user which is being
authenticated at this point, it is the machine.
Notice that you had the same issue when you tried to manually mount.
In my testing, my shared directory was not locked down, which meant the
mount succeeded and then the ls was able to go across with my
credentials.
I think you ACL is too restrictive - which adding nobody
effectively shows.
I'm not sure I agree with that. The share in question is for my (I'm
Shawn) eyes only. I have multiple users on the system and don't want
them to access my files. Is there a way to prevent others from
accessing my files yet have less-restrictive ACLs?
I don't do ACLs. :->
Try this, create another share and do not add an ACL. Instead, use chmod(1)
to set your permissions:
[th199...@ultralord ~]> touch shawn
[th199...@ultralord ~]> ls -la shawn
-rw-r--r-- 1 th199096 staff 0 Apr 20 11:22 shawn
[th199...@ultralord ~]> chmod 700 shawn
[th199...@ultralord ~]> ls -la shawn
-rwx------ 1 th199096 staff 0 Apr 20 11:22 shawn
[th199...@ultralord ~]>
Then try to mount it.
The other piece of the puzzle is that root will get mapped to be
the anon
user id, which is also "nobody".
I was under the impression that autofs would send my UID across the
wire... Meaning not mapping as nobody. Maybe LDAP is after all the
answer here?
See above, but the issue isn't where we get your UID, but the UID we use
during the
mount portion.
_______________________________________________
nfs-discuss mailing list
[email protected]
