I'm hoping I'm mistaken, but it seems to be quite hard to set up a
secure, working, internet-accessible Darcs server that allows
relatively untrusted users to push changes. As I understand it the
options are:

1. HTTP: A bit sniffable. Authentication not supported. Read-only.
2. HTTPS: Authentication not supported. Not supported at all on
Windows (Darcs doesn't trust any root certs). Read-only.
3. SSH: Not secure, as it requires giving people shell access to the
server. Allows file-edits that don't comply with version control.
4. File-share: Firewalls and authentication issues can make this
tricky, and it's long-winded. Allows file-edits that don't comply with
version control.
5. Email (to accompany HTTP/HTTPS): Requires manual effort for patch
application or can't return sensible error messages (if it can, then
it can probably also serve as a spamming host).

The other version control systems I'm aware of tend to have had a
server built for them, which allows for seamless authentication and
read/write access, without having to give users shell access of any
kind. Does Darcs have anything like that?

Note: Some of the users I support are using shared accounts on some
machines, so solutions that use environment variables would be hard to
use.

G.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users

Reply via email to