[scponly] PATCH: support for multiple users with the same uid

[Kaleb Pederson]

On Monday 11 June 2007, Steve Kehlet wrote:
> /bonk why do you always think of these things the moment after
> sending an email...
>
> I guess a solution in that case would be to create a second acl for
> the user on his directories, giving him full access.

In the cases where I have used it, the containing folder was setgid to a valid 
group for the user in question.  Thus, every file (and directory) that was 
created was owned by that group.  I just had to make sure that the daemon 
created the files such that the user had group read and write permissions.  
But, as you just pointed out, you could just as easily add an ACL that 
granted the user permissions.

--Kaleb

> > Ahh, I like the idea, thanks.  I think in my case though, the
> > daemon creates new files, and they'd be created with the wrong
> > ownership and permissions.  Then the users might run into
> > permissions problems, depending on what they tried to do.  Though
> > maybe if they owned the containing directory it wouldn't really
> > matter for uploading/downloading stuff via sftp, not sure...
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : https://lists.ccs.neu.edu/pipermail/scponly/attachments/20070612/87ae76d8/attachment.bin