public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
To: GCC <gcc@gcc.gnu.org>
Subject: Re: Need GCC 3.3.6 PGP Signing Public Key
Date: Sun, 29 May 2005 18:53:00 -0000	[thread overview]
Message-ID: <87r7fpkiw2.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <Pine.BSF.4.62.0505281752000.74808@acrux.dbai.tuwien.ac.at> (Gerald Pfeifer's message of "Sat, 28 May 2005 17:55:18 +0200 (CEST)")

Gerald Pfeifer <gerald@pfeifer.com> writes:

> For example, I could easily create a key for Gabriel Dos Reis
> <gdr@pfeifer.com> and upload it to the key servers, or some evil hacker
> could do something similar.

And, in fact, people do; this is not just theoretical.  There is an extra
(unsigned) key for Russ Allbery <rra@stanford.edu> on the keyservers that
I had nothing to do with.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

      parent reply	other threads:[~2005-05-29 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 23:43 imacat
2005-05-28 18:08 ` Gerald Pfeifer
2005-05-28 19:07   ` Gabriel Dos Reis
2005-05-28 20:23     ` Gerald Pfeifer
2005-05-28 22:52       ` imacat
2005-05-29 18:53       ` Russ Allbery [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=87r7fpkiw2.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).