Yes, I reported that this is the cas,e IIRC starting 13 May. I have purchased a new certificate, but not taken the time to install it, as it was not "dead simple" (why should it be?)
Cheers Niclas On Thu, May 22, 2008 at 9:02 PM, Hendy Irawan <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED]:~/project/ops4j$ svn co > https://scm.ops4j.org/repos/ops4j/projects/base base > Error validating server certificate for 'https://scm.ops4j.org:443': > - The certificate is not issued by a trusted authority. Use the > fingerprint to validate the certificate manually! > - The certificate has expired. > Certificate information: > - Hostname: scm.ops4j.org > - Valid: from Sat, 13 May 2006 08:17:59 GMT until Tue, 13 May 2008 08:17:59 > GMT > - Issuer: http://www.starfieldtech.com/repository, Starfield Technologies, > Inc., Scottsdale, Arizona, US > - Fingerprint: a2:36:27:3d:f3:84:97:df:de:88:3a:a6:b4:c7:04:37:45:a7:e9:af > (R)eject, accept (t)emporarily or accept (p)ermanently? p > svn: PROPFIND request failed on '/repos/ops4j/projects/base' > svn: PROPFIND of '/repos/ops4j/projects/base': Server certificate > verification failed: certificate has expired, issuer is not trusted > (https://scm.ops4j.org) > > > -- > Best regards, > Hendy Irawan > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
