Exporting my certificate as .pfx from IE7 worked and I am now able to use svn without Krystian Bacławski's workaround.
Isn't this just another workaround for the original issue, though? While recent implementations of PFX conform to the PKCS#12 spec, aren't they still different than the .p12 keys exported from a Mozilla product (or others)? I know that my .p12 key and the .pfx key files are not the same size even though they are equivalent (I had to import the old .p12 key into IE before I could export it as a .pfx). Thanks, Tim Flink -----Original Message----- From: Dumont, Dominique Sent: Friday, August 29, 2008 10:17 AM To: Flink, Timothy Cc: [EMAIL PROTECTED] Subject: Re: Bug#480041: Still happening for me "Flink, Timothy" <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED]:~/code$ svn co https://secure-svn-server.com/svn/blah > Authentication realm: https://secure-svn-server.com:443 > Client certificate filename: <path to .p12 key> Re-export your certificate (possibly from IE as I did) so as to get a .pfx file (and not a .p12 file), change subversion's server config to point to the new file and retry. It's now working for me. HTH -- Dominique Dumont "Delivering successful solutions requires giving people what they need, not what they want." Kurt Bittner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
