public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Gerald Pfeifer <gerald@pfeifer.com>
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 19:07:00 -0000	[thread overview]
Message-ID: <m3y89zuw7k.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <Pine.BSF.4.62.0505281723520.74808@acrux.dbai.tuwien.ac.at>

Gerald Pfeifer <gerald@pfeifer.com> writes:

| On Sat, 28 May 2005, imacat wrote:
| >     This is imacat from Taiwan.  I was downloading GCC 3.3.6.  I saw it
| > was signed by PGP key 902C9419, and it displayed its owner as Gabriel
| > Dos Reis.  But I can't find any other public source that can prove this
| > key as her/his, not even on GCC website http://gcc.gnu.org/ or Savannah. 
| > Did I miss something?  Is that key 902C9419 really her/his?  Could
| > someone confirm about this, or better, publish that PGP signing key
| > somewhere, on GCC website?  Thank you.
| 
| 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.

| 
| Many of us will meet at the GCC Summit next month in Ottawa, and I
| suggest we all make sure to improve the web of trust in the GCC
| community (and especially as far as the release managers are concerned).

I'm planning to be there.

-- Gaby

  reply	other threads:[~2005-05-28 15:44 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 [this message]
2005-05-28 20:23     ` Gerald Pfeifer
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=m3y89zuw7k.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --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).