From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v2 1/4] meson: bump version to 0.47.1
Date: Wed, 18 Jul 2018 06:03:04 +0300 [thread overview]
Message-ID: <87k1pt5jpz.fsf@tkos.co.il> (raw)
In-Reply-To: <20180717232319.75bc4941@gmx.net>
Hi Peter,
Peter Seiderer writes:
> On Tue, 17 Jul 2018 23:02:32 +0300, Baruch Siach <baruch@tkos.co.il> wrote:
>> Peter Seiderer writes:
>>
>> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>> > ---
>> > Notes:
>> > Hash not checked against the pgp signature, tried
>> > $ gpg --verify meson-0.47.1.tar.gz.asc meson-0.47.1.tar.gz
>> > gpg: Signature made Di 10 Jul 2018 23:28:12 CEST
>> > gpg: using RSA key 95181F4EED14FDF4E41B518D3BF4693BFEEB9428
>> > gpg: Can't check signature: No public key
>> >
>> > Any advice which public key is used to sign the meson package?
>>
>> The key ID is shown in the message above. You can import the key and
>> verify with:
>>
>> gpg --recv-keys 95181F4EED14FDF4E41B518D3BF4693BFEEB9428
>> gpg --verify meson-0.47.1.tar.gz.asc
>>
>> gpg: Signature made Wed 11 Jul 2018 12:28:12 AM IDT
>> gpg: using RSA key 95181F4EED14FDF4E41B518D3BF4693BFEEB9428
>> gpg: Good signature from "Jussi Pakkanen <jpakkane@gmail.com>" [marginal]
>
> Thanks for the hint!
>
> I get the same warning as Eric:
>
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 9518 1F4E ED14 FDF4 E41B 518D 3BF4 693B FEEB 9428
>
> To 'trust' the signing I need a trust-chain (or an 'official' signed public key) or
> an second source where I can compare the fingerprint against? Your seem to have
> an 'marginal' trust-chain?
I enabled TOFU[1] in my gpg configuration. TOFU makes more sense to me
for my use of gpg.
baruch
[1] https://www.gnupg.org/ftp/people/neal/tofu.pdf
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-07-18 3:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 19:16 [Buildroot] [RFC v2 1/4] meson: bump version to 0.47.1 Peter Seiderer
2018-07-17 19:16 ` [Buildroot] [RFC v2 2/4] meson: change from global to per package cross-compilation.conf Peter Seiderer
2018-07-17 19:16 ` [Buildroot] [RFC v2 3/4] libdrm: change to meson build system Peter Seiderer
2018-07-17 19:16 ` [Buildroot] [RFC v2 4/4] libinput: bump version to 1.11.0 and convert to meson build Peter Seiderer
2018-07-17 20:02 ` [Buildroot] [RFC v2 1/4] meson: bump version to 0.47.1 Baruch Siach
2018-07-17 21:23 ` Peter Seiderer
2018-07-18 3:03 ` Baruch Siach [this message]
2018-07-18 19:46 ` Peter Seiderer
2018-07-17 20:23 ` Eric Le Bihan
2018-07-18 20:16 ` Peter Seiderer
2018-07-19 6:00 ` Eric Le Bihan
2018-07-19 20:48 ` Peter Seiderer
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=87k1pt5jpz.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox