[Issue 681] New - Problem with unvalid SourceForge certificates

http://rapidsvn.tigris.org/issues/show_bug.cgi?id=681
                 Issue #|681
                 Summary|Problem with unvalid SourceForge certificates
               Component|rapidsvn
                 Version|0.10
                Platform|Macintosh
              OS/Version|Mac OS X
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|ui
             Assigned to|issues@rapidsvn
             Reported by|dominus






------- Additional comments from [email protected] Mon Oct  5 07:18:43 -0700 2009 -------
When updating a repository on SourceForge you get the error dialog

"RapidSVN Error
Could not unlock mutex (error 0: Unknwon error: 0)"

followed by the more explanatory dialog that tells you that the certificate by
sourceforge is not certified and if you want to certify the fingerprint manually
with the options: Always, For Now, Cancel

When I click on "Always", usually it works for the my "current update session".
Sometimes it doesn't and I get the certificate dialog again on another
SourceForge repository (but not the mutex unlock error). But on closing down
RapidSVN and restarting I get both the mutex unlock eror and the certificate
dialog again.

It seems to me that RapidSVN is forgetting that it should remember that
certificate. On Windows this works, on first start accessing a SF repository I
get asked to accept the certificate and then on next update I get asked again
but after that no more.

------------------------------------------------------
http://rapidsvn.tigris.org/ds/viewMessage.do?dsForumId=670&dsMessageId=2403664

To unsubscribe from this discussion, e-mail: [[email protected]].