Grant Husbands wrote:
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.
I haven't noticed the HTTPS certificate issue on Windows, but then I
just realized I never tried that.
By "authentication not supported", I assume you tried "HTTP Digest Auth"
and it doesn't work? (That is, a URL of the form
http://user:[email protected])
Both sound like features that should be supported in the HTTP libraries
that darcs uses, and maybe should be reported "upstream"...
Beyond that, you can do "darcs send" to HTTP POST (in darcs >= 2.0),
which can provide HTTP-based change pushing. You simply add a
_darcs/prefs/post with an HTTP URL. The POST response from darcs is then
the email that darcs send generates (so you'll need an email parsing
library like Python's email module). Patches can be authenticated in
"the usual ways" for darcs send: signed by GPG or (Open)SSL certificates.
Darcs send to HTTP POST seems to me to be the most useful for
"relatively untrusted users to push changes".
--
--Max Battcher--
http://worldmaker.net
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
