From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] let's stop using short gpg key ids, that's insecure
Date: Mon, 02 Jan 2012 15:47:23 +0100 [thread overview]
Message-ID: <4F01C37B.6000305@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
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.
Note it's about IDs, i.e. 0x30427902 vs. 0xB9442D9430427902 (it's short
and long ID of my current key), not the keys themselves. That means no
need to change keys, just change the way we display them on web pages
and possibly in other places.
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?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next reply other threads:[~2012-01-02 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 14:47 "Paweł Hajdan, Jr." [this message]
2012-01-02 15:20 ` [gentoo-project] let's stop using short gpg key ids, that's insecure Chí-Thanh Christopher Nguyễn
2012-01-02 17:17 ` Michał Górny
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=4F01C37B.6000305@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-project@lists.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