Hi, I just recently noticed this problem:
rich...@shuttlex:~# pkg publisher extra
Éditeur : extra
Alias : None
URI d'origine : https://pkg.sun.com/opensolaris/extra/
Clé SSL : /var/pkg/ssl/OpenSolaris_extras.key.pem
Certificat SSL : /var/pkg/ssl/OpenSolaris_extras.certificate.pem
Date de début de validité du certificat : 5 mai 2010 06:09:51
Date d'expiration du certificat : 13 juin 2011 06:09:51
UUID client : 00000000-19e4-cb88-0111-000000000000
Mise à jour du catalogue : 17 août 2010 17:33:10
Activation : Oui
rich...@shuttlex:~# pkg refresh --full extra
pkg : les catalogues 0/1 ont été mis à jour :
Framework error: code: 60 reason: SSL certificate problem, verify that the CA
cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
failed
URL: 'https://pkg.sun.com/opensolaris/extra/catalog/0/'.
I noticed that last year in the pkg-discuss list what seems to be the same
problem:
[pkg-discuss] Problems trying to access the /extra repository.
johansen at sun.com johansen at sun.com
Tue Oct 6 10:44:44 PDT 2009
* Previous message: [pkg-discuss] Problems trying to access the /extra
repository.
* Next message: [pkg-discuss] Problems trying to access the /extra
repository.
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Oct 06, 2009 at 07:42:56AM -0700, Rich Burridge wrote:
> $ pfexec pkg set-authority -k /var/pkg/ssl/OpenSolaris_extras.key.pem -c
> /var/pkg/ssl/OpenSolaris_extras.certificate.pem -O
> https://pkg.sun.com/opensolaris/extra/ extra
> pkg: The origin URIs for 'extra' do not appear to point to a valid pkg
> server.
> Please check the server's address and client's network configuration.
> Additional details:
>
> Unable to contact valid package server:
> https://pkg.sun.com/opensolaris/extra/
> Encountered the following error(s):
> Transport errors encountered when trying to contact depot server.
> Reported the following errors:
> Framework error: code: 60 reason: SSL certificate problem, verify that
> the CA cert is OK. Details:
> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
> verify failed
> URL: 'https://pkg.sun.com/opensolaris/extra/versions/0/'.
>
> Hints to where I'm going wrong would be appreciated.
and it appeared that the problem was resolved with:
[pkg-discuss] Problems trying to access the /extra repository.
Rich Burridge Rich.Burridge at Sun.COM
Tue Oct 6 12:51:51 PDT 2009
* Previous message: [pkg-discuss] Problems trying to access the /extra
repository.
* Next message: [pkg-discuss] Problems trying to access the /extra
repository.
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
johansen at sun.com wrote:
> This is very odd. The directory should contain a key file, as yours
> does, but it should also have a symlimk.
>
> If you perform the following as root in /usr/share/pkg/cacert, I think
> this should solve your problem:
>
> ln -s Verisign_Class_3_Public_Primary_Certification_Authority-G2.pem
> 72fa7371.0
>
> Just for reference, a ls -l on my machine looks like this:
>
> lrwxrwxrwx 1 root root 62 Aug 19 16:23 72fa7371.0 ->
> Verisign_Class_3_Public_Primary_Certification_Authority-G2.pem
> -r--r--r-- 1 root bin 1119 Aug 19 16:23
> Verisign_Class_3_Public_Primary_Certification_Authority-G2.pem
>
> HTH,
>
It sure did. Working now.
Thanks!
------------------------------
unfortunately, I checked my cacert directory and it seems alright:
rich...@shuttlex:~# ls -l /usr/share/pkg/cacert/
total 3
lrwxrwxrwx 1 root root 62 2010-02-20 08:07 72fa7371.0 ->
Verisign_Class_3_Public_Primary_Certification_Authority-G2.pem
-r--r--r-- 1 root bin 1119 2009-12-20 02:29
Verisign_Class_3_Public_Primary_Certification_Authority-G2.pem
Is there any other potential solution, or is this part of the recent «bad» news
regarding opensolaris.
Thanks in advance,
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
