From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/ca-certificates: don't hash certificates.crt
Date: Mon, 18 Jun 2018 16:39:31 +0200 [thread overview]
Message-ID: <20180618163931.4531ccb3@windsurf> (raw)
In-Reply-To: <CAFGQKxeOmRCBUu7XFCDkpRbFV51F0=A8htjRMc75rKQA8_VtoQ@mail.gmail.com>
Hello,
On Mon, 18 Jun 2018 10:51:34 +0100, Martin Bark wrote:
> > output/target$ ls -l etc/ssl/certs/128805a3.0
> > lrwxrwxrwx 1 thomas thomas 35 Jun 17 20:58 etc/ssl/certs/128805a3.0 -> EE_Certification_Centre_Root_CA.pem
>
> Did you check other hashes under etc/ssl/certs/ ? Check for any hashes
> that link to ca-certificates.crt. I suspect you have a different hash
> pointing to ca-certificates.
There are no files in /etc/ssl/certs that are symlinks to
ca-certificates.crt:
output/target$ ls -l etc/ssl/certs/| grep ca-certificates.crt
-rw-r--r-- 1 thomas thomas 207436 Jun 18 15:30 ca-certificates.crt
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-18 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 22:05 [Buildroot] [PATCH v2 0/3] package/ca-certificates improvements Martin Bark
2018-06-16 22:05 ` [Buildroot] [PATCH v2 1/3] package/ca-certificates: don't hash certificates.crt Martin Bark
2018-06-17 19:25 ` Thomas Petazzoni
2018-06-18 9:51 ` Martin Bark
2018-06-18 14:39 ` Thomas Petazzoni [this message]
2018-06-21 22:04 ` Martin Bark
2018-10-21 13:15 ` Arnout Vandecappelle
2018-10-21 13:38 ` Arnout Vandecappelle
2018-10-21 14:03 ` Martin Bark
2018-10-24 12:32 ` Peter Korsgaard
2018-06-16 22:06 ` [Buildroot] [PATCH v2 2/3] package/ca-certificates: fix rebuilds Martin Bark
2018-06-16 22:06 ` [Buildroot] [PATCH v2 3/3] package/ca-certificates: create ca-certificates.crt reproducibly Martin Bark
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=20180618163931.4531ccb3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.