CAcert System Admins discussion list

[Wytze van der Raay <wytze AT deboca.net>]

Op 22-4-2012 17:28, Michael Tänzer schreef:
> today a user mailed me that he was unable to access a document on SVN
> saying he got a 404. It really was a handshake alert not a 404 but that
> still has me wonder why we only allow read access to the SVN if the user
> authenticates via client cert.
> 
> The document in question was:
> https://svn.cacert.org/CAcert/HowTo/How%20to%20translations%20for%20CAcert%20applications.pdf

If you read the document via http://svn.cacert.org/... rather than
https, no certificate is needed.
And if you really want https for privacy during transport, it's also
possible to use https://nocert.svn.cacert.org/... for reading.

The https interface also provides write access (via webdav), so I
think that is the reason to insist on some form of authentication.
svn.cacert.org and cert.svn.cacert.org require client certificate
authentication up-front, nocert.svn.cacert.org supports username/
password authentication, which will be delayed until authentication
is really needed.

Regards,
-- wytze

Attachment: smime.p7s
Description: S/MIME cryptografische ondertekening