Re: [rdiff-backup-users] Re: backup project to a quota limited directory

[Chris Wilson]

Hi Ahmed,

On Tue, 13 Feb 2007, Ahmed Kamal wrote:

> thanks a lot for the help. I'm afraid having people in just one group is 
> not really possible, as a group is a project, and people will be working 
> on multiple projects, that's just a fact.

Well, rdiff-backup can't do exactly what you want out of the box, that's 
just a fact (afaik).

> I wasn't aware ssh keys could restrict users in certain directories like
> that, any pointers please?

man sshd and search for "authorized key file format"

man rdiff-backup and search for --restrict

> It still looks hackish though.

Unix is one big hack, may as well get used to it :-)

> Isn't there any client side option to force running some command 
> "newgrp" in this case on the server, before the actual transfer begins ?

The problem is that rdiff-backup won't just create the files and leave 
them alone, it will try to change their group to match the one on the 
client.

Try the --group-mapping-file option (man rdiff-backup) on the SSH key to 
map all groups to the same one. Each key can have its own group mapping, 
so if users log in with different keys, their files get mapped to a 
different group (whatever group they were on the client).

Or you could enforce that all files for a particular project have the same 
group (of the project) on the client before uploading, with chmod -R.

Cheers, Chris.
--
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
\ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |