Re: Subclipse/Win and self signed SSL certificate

> Michael Klemm wrote:
>> Checking out using the shell client svn works perfectly, but
>> Subclipse refuses to list the repository with
>>
>> | svn: PROPFIND request failed on '/svn/parmol'
>> | svn: PROPFIND of
>> '/svn/parmol': Server certificate verification failed: issuer is
>> not trusted (https:....

Ben Collins-Sussman wrote:
> I'm guessing that the subclipse folks haven't fully implemented the
> SSL callback dialogues required by the svn core libraries? Not sure.
> Either way, Subclipse is a separate project. Resend your mail to
> users@subclipse.tigris.org.

We use a somewhat similar setup here, but we encountered no problems
with subclilpse.

We did the following
- create a "in-house-snakeoil-CA"-Certificate (self signed)
- sign the webserver certificate with this CA-cert
- create a certificate for every user
- sign this with the CA-cert as well
- convert this user cert into pkcs12-format (with openssl)
- import this (*.p12) into web browser (for Mozilla) resp. into windows
   certificate store (for IE/Win) for repository access via https
- declare it in the runtime configuration area of subversion in the
   "servers" file.

After this, the commandline client works without any
password/certificate prompt. tortoise, rapidSVN and subclipse
do the same.

hope this helps

-- 
Hermann Vosseler
---------------------------------------------------------------
Hermann Voßeler
Baader Wertpapierhandelsbank AG
Weihenstephaner Straße 4
D-85716 Unterschleißheim
eMail: hermann.vosseler@baaderbank.de
Internet: www.baaderbank.de
---------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org