You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Jencks <dj...@gluecode.com> on 2005/01/26 23:06:11 UTC
Is this really the correct svn certificate?
I am now getting a non-expired certificate:
Error validating server certificate for 'https://svn.apache.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: svn.apache.org
- Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
- Issuer: http://www.starfieldtech.com/repository, Starfield
Technologies, Inc., Scottsdale, Arizona, US
- Fingerprint:
19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
Is this still apache or has svn been hijacked?
thanks
david jencks
Re: Is this really the correct svn certificate?
Posted by Jacek Laskowski <jl...@apache.org>.
David Jencks wrote:
> I was given a choice of rejecting, accepting temporarily, or accepting
> permanently. Before Jeremy's reassurance I accepted temporarily, but
> have now accepted permanently
Doh! I was doing update via maven m:update and didn't even think to use
svn itself :( I used so much to use maven m:update that I completely
forgot about it. It's so addictive ;) Shame on me! Thanks Dave.
> david jencks
Jacek
Re: Is this really the correct svn certificate?
Posted by David Jencks <dj...@gluecode.com>.
I was given a choice of rejecting, accepting temporarily, or accepting
permanently. Before Jeremy's reassurance I accepted temporarily, but
have now accepted permanently
thanks
david jencks
On Jan 29, 2005, at 2:24 PM, Jacek Laskowski wrote:
> Jeremy Boynes wrote:
>> David Jencks wrote:
>>> I am now getting a non-expired certificate:
>>>
>>> Error validating server certificate for 'https://svn.apache.org:443':
>>> - The certificate is not issued by a trusted authority. Use the
>>> fingerprint to validate the certificate manually!
>>> Certificate information:
>>> - Hostname: svn.apache.org
>>> - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007
>>> GMT
>>> - Issuer: http://www.starfieldtech.com/repository, Starfield
>>> Technologies, Inc., Scottsdale, Arizona, US
>>> - Fingerprint:
>>> 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
>>>
>>>
>>> Is this still apache or has svn been hijacked?
>>>
>>> thanks
>>> david jencks
>> I believe so - at least the cert is recognized by both Firefox and IE.
>> My guess would be that SVN does not have the appropriate root CA
>> (http://www.valicert.com) available.
>
> I'm getting the error too, and don't have any idea what to do. Having
> seen the commits I think it's only me who can't work it out. What are
> the steps to get rid of it?
>
>> Jeremy
>
> Jacek
>
Re: Is this really the correct svn certificate?
Posted by Jacek Laskowski <jl...@apache.org>.
Jeremy Boynes wrote:
> David Jencks wrote:
>
>> I am now getting a non-expired certificate:
>>
>> Error validating server certificate for 'https://svn.apache.org:443':
>> - The certificate is not issued by a trusted authority. Use the
>> fingerprint to validate the certificate manually!
>> Certificate information:
>> - Hostname: svn.apache.org
>> - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
>> - Issuer: http://www.starfieldtech.com/repository, Starfield
>> Technologies, Inc., Scottsdale, Arizona, US
>> - Fingerprint:
>> 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
>>
>>
>> Is this still apache or has svn been hijacked?
>>
>> thanks
>> david jencks
>
>
> I believe so - at least the cert is recognized by both Firefox and IE.
> My guess would be that SVN does not have the appropriate root CA
> (http://www.valicert.com) available.
I'm getting the error too, and don't have any idea what to do. Having
seen the commits I think it's only me who can't work it out. What are
the steps to get rid of it?
> Jeremy
Jacek
Re: Is this really the correct svn certificate?
Posted by Geir Magnusson Jr <ge...@4quarters.com>.
On Jan 26, 2005, at 5:26 PM, Jeremy Boynes wrote:
> David Jencks wrote:
>> I am now getting a non-expired certificate:
>> Error validating server certificate for 'https://svn.apache.org:443':
>> - The certificate is not issued by a trusted authority. Use the
>> fingerprint to validate the certificate manually!
>> Certificate information:
>> - Hostname: svn.apache.org
>> - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
>> - Issuer: http://www.starfieldtech.com/repository, Starfield
>> Technologies, Inc., Scottsdale, Arizona, US
>> - Fingerprint:
>> 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
>> Is this still apache or has svn been hijacked?
>> thanks
>> david jencks
>
> I believe so - at least the cert is recognized by both Firefox and IE.
> My guess would be that SVN does not have the appropriate root CA
> (http://www.valicert.com) available.
Weird - my svn client thinks it's just peachy...
>
> --
> Jeremy
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
Re: Is this really the correct svn certificate?
Posted by Jeremy Boynes <jb...@apache.org>.
David Jencks wrote:
> I am now getting a non-expired certificate:
>
> Error validating server certificate for 'https://svn.apache.org:443':
> - The certificate is not issued by a trusted authority. Use the
> fingerprint to validate the certificate manually!
> Certificate information:
> - Hostname: svn.apache.org
> - Valid: from Jan 26 14:18:55 2005 GMT until Jan 26 14:18:55 2007 GMT
> - Issuer: http://www.starfieldtech.com/repository, Starfield
> Technologies, Inc., Scottsdale, Arizona, US
> - Fingerprint: 19:51:6b:9b:03:78:2b:4b:0f:02:77:ed:2a:85:ef:93:ed:b6:ff:95
>
>
> Is this still apache or has svn been hijacked?
>
> thanks
> david jencks
I believe so - at least the cert is recognized by both Firefox and IE.
My guess would be that SVN does not have the appropriate root CA
(http://www.valicert.com) available.
--
Jeremy