On Tue, Apr 22, 2008 at 10:32:07PM +0200, Johannes Waldmann <[EMAIL PROTECTED]> wrote: > What's the current best practice for setting up > a repository for remote write acces > (and not giving full shell access) > > It seems ssh is required, so scponly does not work. > This is quite the show-stopper. > > For CVS, one could apparently use (in sshd_config) > Match User foo ; ForceCommand cvs server .
you can write a wrapper yourself as well, it's not that hard. create an account and add the followings to the user's ~/.ssh/authorized_keys: command="darcs-shell username" <original key> this way you can have a system-wide darcs user and you can use many keys for many users while not spamming /etc/passwd. you can write darcs-shell based on an svn or git example. i wrote one for git, which is available at: http://git.frugalware.org/repos/vmexam/git/git-shell2 (sorry for the git hype, i don't have time to modify it for darcs atm, but i'm sure it wouldn't be hard.)
pgpnBW3NSQQ1S.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
