From: richard.purdie@linuxfoundation.org
To: kai.kang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] nss: fix non-determinism when create blank certificate
Date: Thu, 11 Oct 2018 19:55:33 +0100 [thread overview]
Message-ID: <ae1bccd3a002637aef132d5cee1316bfe717e018.camel@linuxfoundation.org> (raw)
In-Reply-To: <eedd956a3e7af4d2c64033d1b06944036c5d6536.1539267480.git.kai.kang@windriver.com>
On Thu, 2018-10-11 at 22:24 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> It uses tool certutil from nss to create a blank certificate. But the
> checksum of output file key4.db changes every time:
>
> $ certutil -N -d sql:. --empty-password
> $ md5sum *
> f9dac2cfcb07cc8ca6db442a9a570906 cert9.db
> b892c5ff7c1977d4728240b0cf628377 key4.db
> 7b9136cb03f07ae62eb213a5239fda71 pkcs11.txt
> $ rm *
>
> $ certutil -N -d sql:. --empty-password
> $ md5sum *
> f9dac2cfcb07cc8ca6db442a9a570906 cert9.db
> 405d55178e866a115c1aa975fccfa764 key4.db
> 7b9136cb03f07ae62eb213a5239fda71 pkcs11.txt
>
> Provide pre-created blank database files to fix non-determinism
> issue.
> And these files are from nss qemux86-64 build.
I agree with this however can we leave a comment in the recipe about
why we're including these and instructions on how to rebuild them
please?
Cheers,
Richard
next prev parent reply other threads:[~2018-10-11 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 14:24 [PATCH 0/1] nss: fix non-determinism when create blank certificate kai.kang
2018-10-11 14:24 ` [PATCH 1/1] " kai.kang
2018-10-11 18:55 ` richard.purdie [this message]
2018-10-12 1:25 ` Kang Kai
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=ae1bccd3a002637aef132d5cee1316bfe717e018.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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