public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: imacat <imacat@mail.imacat.idv.tw>, GCC <gcc@gcc.gnu.org>
Subject: Re: Need GCC 3.3.6 PGP Signing Public Key
Date: Sat, 28 May 2005 20:23:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.62.0505281752000.74808@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <m3y89zuw7k.fsf@uniton.integrable-solutions.net>

On Sat, 28 May 2005, Gabriel Dos Reis wrote:
>| Gaby added his key to the website now, but I agree that we should make
>| sure the keys are sufficiently well signed by other members of the free
>| software (or open source) community.
> I'm a bit surprised because I uploaded my new key last december,
> shortly before signing 3.3.5.

As far as I understand, it's not a question of these keys being available 
on a key server, but having sufficiently many signatures and proper paths
of trust.

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.

>| Many of us will meet at the GCC Summit next month in Ottawa
> I'm planning to be there.

Excellent.  Let's make sure you'll get one or two dozen of signatures
for your PGP key there! :-)

Gerald

  reply	other threads:[~2005-05-28 15:55 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 [this message]
2005-05-28 22:52       ` imacat
2005-05-29 18:53       ` Russ Allbery

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=Pine.BSF.4.62.0505281752000.74808@acrux.dbai.tuwien.ac.at \
    --to=gerald@pfeifer.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=imacat@mail.imacat.idv.tw \
    /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).