Hi Daniel, On Sat, Mar 1, 2014 at 5:06 AM, Daniel Widdis <wid...@gmail.com> wrote: > I recently upgraded from 1.8.5 to 1.8.8 via macports. The new version > refused to permanently accept my self-signed certificate, citing an "unknown > error". > > Certificates generated on Windows 2008 Server using VisualSVN 2.7.4. > > Hostname is a numeric IP on a VPN (192.168.100.59) > > Client is Mac OS X 10.9.1 (Mavericks) with svn installed via Macports: > subversion @1.8.5_1+universal (active) <---- this setup works > subversion @1.8.8_0+no_bdb+universal <---- this setup fails > > Under 1.8.8: > $ svn update > Updating '.': > Error validating server certificate for 'https://192.168.100.59:443': > - The certificate has an unknown error. > Certificate information: > - Hostname: 192.168.100.59 > - Valid: from Mar 1 02:21:16 2014 GMT until Feb 27 02:21:16 2024 GMT > - Issuer: > - Fingerprint: BE:C4:65:B6:0E:BD:5C:EE:F4:DB:A9:E1:EB:AE:B6:BC:43:F2:E7:5E > (R)eject or accept (t)emporarily? t > At revision 46.
Could you send: - the output of: $ openssl s_client -connect 192.168.100.59:443 - and/or create a self signed key + cert using your method that fails with svn 1.8.8 ? This should give us the necessary extra info to simulate your issue. Note: since you're using a self signed certificate this log/key-cert pair shouldn't contain any private info, but if you prefer you can send them to me privately. > Under 1.8.5 with no other changes: > $ svn update > Updating '.': > At revision 46. > regards, Lieven