0000271: SSL Client certificates with blank/no password dont work (Incompatibility with svn)

Notes
(0000509) oka (administrator) 2008-10-03 19:17	Hello, Thank you for reporting this issue. AFAIR, no-passphrase protected certificates worked for me. Could it happen that you have another certificate and passphrase defined in the [global] group or in system global configuration file (/etc/subversion/servers)? Also, empty passphrase ("") and no passphrase (null) could be treated differently by Java certificate loader. I'm not saying there is no bug, but would like to get more details on the problem.

(0000510) cavanaug (reporter) 2008-10-06 07:40	Good question on empty vs null. Honestly, when I exported them using openssl I just hit return at the prompt for password, so I dont know what it used, presumably empty??? Im traveling for a couple days but Ill try to get some additional information to you. Ill plan on providing the following. - Full copy of svn servers file - Shell window history of using regular svn, and jsvn showing success/failures Is there anything else I can do in terms of turning on specially logging/debugging in jsvn so I can provide better diagnostic information??

(0000512) oka (administrator) 2008-10-11 01:23	Hello, After some additional investigations I figured out that inability to load SSL certificate without password is JDK bug, still not fixed in JDK 1.6. However, I think we could workaround this problem providing custom implementation for one of SSL-related interface. What I miss is a server with SSL client cert authentication enabled. I tried to set up one - but strangely it allows me to log in both with certificate and without, so I couldn't really say whether my workaround works well. Is it possible to get test RO access to your repository with unprotected client certificate? This will help a log in fixing this problem. Thanks!

(0000796) cavanaug (reporter) 2010-03-25 06:43	After further examination this appears to be a problem with PKCS12 certificates that: Have a blank passphrase or Have a blank export password I think the only recommendation now is to document this somewhere and to generate a useful error message (via jsvn) if certificates are encountered like that.

Issue History
Date Modified	Username	Field	Change
2008-10-02 01:17	cavanaug	New Issue
2008-10-02 02:08	oka	Status	new => assigned
2008-10-02 02:08	oka	Assigned To	=> oka
2008-10-03 19:17	oka	Note Added: 0000509
2008-10-06 07:40	cavanaug	Note Added: 0000510
2008-10-11 01:23	oka	Note Added: 0000512
2010-03-25 06:43	cavanaug	Note Added: 0000796

Relationships