From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Gpg signatures of releases
Date: Mon, 01 Jun 2015 23:51:33 +0200 [thread overview]
Message-ID: <2176353.1XFu4ogKc2@indiana> (raw)
In-Reply-To: <20150601212154.GK27570@hermes.click-hack.org>
El Dilluns, 1 de juny de 2015, a les 23:21:54, Gilles Chanteperdrix va
escriure:
> On Mon, Jun 01, 2015 at 10:52:27PM +0200, Leopold Palomo-Avellaneda wrote:
> > El Dilluns, 1 de juny de 2015, a les 12:17:06, Gilles Chanteperdrix va
> >
> > escriure:
> > > On Mon, Jun 01, 2015 at 12:11:03AM +0200, Leopold Palomo-Avellaneda
wrote:
> > > > Hi,
> > > >
> > > > who sig
> > > >
> > > > http://download.gna.org/xenomai/stable/latest/*.sig
> > > >
> > > > ?
> > >
> > > I do. There used to be a readme file that said so, but it seems it
> > > is no longer displayed by gna. In any case, if you go to the gna
> > > interface you should find the keys of all the project members,
> > > including mine (in fact, gna quarantines an upload if it is not
> > > signed by a project member, or at least is used to). I use the same
> > > key to sign that mail.
> >
> > When I try to download the keyring I get a 0 bytes long file from here:
> >
> > http://gna.org/project/memberlist-gpgkeys.php?group=xenomai
> >
> > I found that the file was signed by this key with this id A9BF7DBA,
> > but I have not found who is the proprietary.
> >
> > gpg: using character set `utf-8'
> >
> > :signature packet: algo 17, keyid 1A972013A9BF7DBA
> > :
> > version 3, created 1411642226, md5len 5, sigclass 0x00
> > digest algo 2, begin of digest 95 30
> > data: [158 bits]
> > data: [158 bits]
> >
> > gpg: Nombre total processat: 0
> >
> > Any idea?
>
> 1- as I told you the key was mine, you can download the key from my
> account:
> http://gna.org/users/gch
in that place, there's only the 7F392711, that it seems the new one.
>
> 2- have you tried gpg --recv-keys ?
Ok, that was the point. I got it, but it was expired.
> I believe this key expired though, my new key is 7F392711, but of
> course the xenomai archives are not signed with it yet.
The 2.6.4 released was signed with the old one.
Anyway, the xenomai keyring at gna is void. Please could you check it?
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150601/40eaa09d/attachment.sig>
next prev parent reply other threads:[~2015-06-01 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 22:11 [Xenomai] Gpg signatures of releases Leopold Palomo-Avellaneda
2015-05-31 22:36 ` Paul
2015-06-01 10:17 ` Gilles Chanteperdrix
2015-06-01 20:52 ` Leopold Palomo-Avellaneda
2015-06-01 21:21 ` Gilles Chanteperdrix
2015-06-01 21:51 ` Leopold Palomo-Avellaneda [this message]
2015-06-01 21:53 ` Gilles Chanteperdrix
2015-06-02 6:28 ` Philippe Gerum
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=2176353.1XFu4ogKc2@indiana \
--to=leo@alaxarxa.net \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.