public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] validate GPG keys by fingerprint
Date: Mon, 13 Nov 2017 23:07:41 +0000	[thread overview]
Message-ID: <1510614461.3441.17.camel@ipfire.org> (raw)
In-Reply-To: <1510613939.3441.16.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

I commented more on the bug report. Everyone who is interested in this
should check that one out...

On Mon, 2017-11-13 at 22:58 +0000, Michael Tremer wrote:
> Thanks. I merged this and so we can work on improving this more...
> 
> On Sun, 2017-11-12 at 15:40 +0100, Peter Müller wrote:
> > Validate GPG keys by fingerprint and not by 8-bit key-ID.
> > 
> > This makes exploiting bug #11539 harder, but not impossible
> > and does not affect existing installations.
> > 
> > Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> > ---
> >  src/pakfire/lib/functions.pl | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/src/pakfire/lib/functions.pl b/src/pakfire/lib/functions.pl
> > index c347916d8..cfb7e5117 100644
> > --- a/src/pakfire/lib/functions.pl
> > +++ b/src/pakfire/lib/functions.pl
> > @@ -34,8 +34,8 @@ use Net::Ping;
> >  package Pakfire;
> >  
> >  # GPG Keys
> > -my $myid = "64D96617";			# Our own gpg-key paks(a)ipfire.org
> > -my $trustid = "65D0FD58";		# gpg-key of CaCert
> > +my $myid = "179740DC4D8C47DC63C099C74BDE364C64D96617";		# Our own gpg-key paks(a)ipfire.org
> > +my $trustid = "A31D4F81EF4EBD07B456FA04D2BB0D0165D0FD58";	# gpg-key of CaCert
> >  
> >  # A small color-hash :D
> >  my %color;

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-11-13 23:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12 14:40 Peter Müller
2017-11-13 22:58 ` Michael Tremer
2017-11-13 23:07   ` Michael Tremer [this message]

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=1510614461.3441.17.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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