Max Battcher wrote: > 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])
I had not tried that, but there'd be a very high risk of password disclosure in use of such a scheme (even if users are being careful to use --no-set-default). > 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. I'll certainly give this a try, this week; thanks for the heads-up. G. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
