public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: openssl WARNING: Skipping duplicate file cert_igca_rsa.pem
Date: Sat, 10 Sep 2011 09:54:06 -0700	[thread overview]
Message-ID: <j4g4nj$ulh$1@dough.gmane.org> (raw)
In-Reply-To: <CAN0CFw3_+W=1sh=pxFFSnCtmDb8SwUe+GmvOmUtjV+UriUFWBQ@mail.gmail.com>

On 09/08/2011 05:51 PM, Grant wrote:
> I just noticed this at the end of my openssl emerge:
> 
> * Running 'c_rehash /etc/ssl/certs/' to rebuild hashes #333069 ...
> WARNING: Skipping duplicate file cert_igca_rsa.pem [ ok ]
>>>> dev-libs/openssl-1.0.0e merged.
> 
> Since SSL is so critical I thought I should run it by you guys.  Is
> this something I should fix?  I get:
> 
> # updatedb && locate cert_igca_rsa.pem
> /old-backup-dir/etc/ssl/certs/cert_igca_rsa.pem
> /etc/ssl/certs/cert_igca_rsa.pem

I notice I have these two symlinks in /etc/ssl/certs:

lrwxrwxrwx 1 root root      9 Sep  7 05:23 3ee7e181.0 -> IGC_A.pem
lrwxrwxrwx 1 root root     17 Sep  7 05:23 3ee7e181.1 -> cert_igca_dsa.pem

After a bit of poking around I see that the ca-certificates package
installs one cert under two different names:

/usr/share/ca-certificates/gouv.fr/cert_igca_rsa.crt
/usr/share/ca-certificates/mozilla/IGC_A.crt

I don't know where the 3ee7e181 symlinks get their names, but I notice
that the duplicate cert is actually the cert_igca_rsa.crt, not the dsa
cert.  That's a bit confusing, but at least it led me to the answer.




  reply	other threads:[~2011-09-10 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09  0:51 [gentoo-user] openssl WARNING: Skipping duplicate file cert_igca_rsa.pem Grant
2011-09-10 16:54 ` walt [this message]
2011-09-10 17:31   ` [gentoo-user] " Grant
2011-09-10 22:56     ` walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='j4g4nj$ulh$1@dough.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox