From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: phajdan.jr@gentoo.org
Subject: Re: [gentoo-project] let's stop using short gpg key ids, that's insecure
Date: Mon, 2 Jan 2012 18:17:52 +0100 [thread overview]
Message-ID: <20120102181752.27c70a7f@pomiocik.lan> (raw)
In-Reply-To: <4F01C37B.6000305@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Mon, 02 Jan 2012 15:47:23 +0100
""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> wrote:
> You've probably read (or should)
> <http://www.asheesh.org/note/debian/short-key-ids-are-bad-news.html>
> which describes why using short gpg key ids is insecure.
Insecure to what? In the same manner, you can say that using your first
and surname is insecure.
> What do you think? Should I file a bug to convert e.g.
> http://www.gentoo.org/proj/en/devrel/roll-call/userinfo.xml ? Or do we
> only have short key IDs in LDAP, which would require everyone to
> submit the full ID?
There's no reason to panic. The trust model of PGP is not based on key
IDs. The short IDs are only used to let users grab our keys at will;
and as the blog post shows, GPG handles repeating key IDs just fine.
I think we can afford that one a million times users will download one
additional key.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-01-02 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 14:47 [gentoo-project] let's stop using short gpg key ids, that's insecure "Paweł Hajdan, Jr."
2012-01-02 15:20 ` Chí-Thanh Christopher Nguyễn
2012-01-02 17:17 ` Michał Górny [this message]
2012-01-05 17:57 ` "Paweł Hajdan, Jr."
2012-01-05 18:21 ` Michał Górny
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=20120102181752.27c70a7f@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=phajdan.jr@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