Re: [securenfs-devel] Mapping all users to a server-side username

[Nathan Y. <na...@yo...>]

David Wolff wrote:

> Nathan Yocom wrote:
>
>>> Actually, I was thinking that we could do this on the client side.
>>> For example:
>>>
>>>   <user localid="*" remoteid="username"/>
>>>
>>> instead of adding the map option.
>>
>>
>>
>>
>> Thats what I am wondering - could it make sense to have it on both 
>> sides?  That way, an administrator could restrict all access from a 
>> certain machine to a particular user account - without having to 
>> trust the client machine to configure it.
>
>
> Well, from a useability standpoint, that might be kind of confusing.
> A client may set up one mapping (local user to remote user), and
> the server would make another mapping.  Perhaps it makes the most
> sense to not allow the server to do any user/group mappings at all.
> It only knows that the client has permissions (a token) to connect
> as a certain user.

True.  I guess I am just a fan of "when in doubt make it an option". 
 Perhaps we should simply have the server do no mapping what so ever in 
initial revisions.  In the future, should it become a requested feature, 
or if we come across a need, we can always add it in (versus doing the 
work and it never being used).

I made your other question a new thread - help keep things organized.

> P.S.  When did you get your own domain (yocom.org)?

;-) Well, my @plu.edu will only last so long after December, and I 
refuse to use hotmail.  So i did some looking, I wanted yo.com but it 
was taken, so I got yocom.org, threw up a website and started using it 
for email.  I do hosting through www.phpwebhosting.com  $10 a mth and 
pretty much unlimited features/use.

Nate