public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-dev-announce] please sign your manifests
Date: Wed, 13 Feb 2013 21:07:57 +0100	[thread overview]
Message-ID: <1993687.8ZKES3KpCB@devil> (raw)
In-Reply-To: <20130212211415.GA4364@linux1>

On Tuesday 12 February 2013 15:14:15 William Hubbs wrote:
> All,
> 
> as preparation for the up-coming cvs->git migration of the portage tree,
> the council is strongly suggesting that from this point forward all
> developers sign their manifests with their gpg key as described in the
> developer's manual [1].
> 
> If you have any questions on this, please feel free to let us know.

As most of us do, I do the commit from another machine, not mine. So, for ssh 
I'm using ssh -A to forward the key and I'm interested to find a way to do it 
for the gpg key.

I found an how-to that uses socat ( http://superuser.com/questions/161973/how-
can-i-forward-a-gpg-key-via-ssh-agent ) but does not work as expected.

This is an example: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-
x86/app-portage/splat/Manifest?revision=1.45&view=markup

The manifest apparently is signed, but there is no really gpg sign.

If someone know how to do it, please let me know.
-- 
Agostino Sarubbo / ago -at- gentoo.org
Gentoo Linux Developer


  parent reply	other threads:[~2013-02-13 20:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130212211415.GA4364@linux1>
2013-02-12 22:52 ` [gentoo-dev] Re: [gentoo-dev-announce] please sign your manifests Michael Weber
2013-02-13 16:13   ` Thomas Sachau
2013-02-12 23:12 ` Michael Weber
2013-02-12 23:28   ` Robin H. Johnson
2013-02-13  7:07     ` Michael Weber
2013-02-13  8:47       ` Ben de Groot
2013-02-13 10:55     ` Markos Chandras
2013-02-13 12:20       ` Michael Weber
2013-02-13 15:31         ` Aaron W. Swenson
2013-02-13 15:47           ` Markos Chandras
2013-02-13 16:35           ` Denis Dupeyron
2013-02-13 16:51             ` Eray Aslan
2013-02-13 17:22             ` Aaron W. Swenson
2013-02-13 17:58               ` Eray Aslan
2013-02-13 18:51                 ` Aaron W. Swenson
2013-02-13 19:37               ` Michael Weber
2013-02-13 17:46     ` "Paweł Hajdan, Jr."
2013-02-13 17:47       ` Diego Elio Pettenò
2013-02-13  0:47 ` Jeroen Roovers
2013-02-13  1:05   ` Jeroen Roovers
2013-02-13  1:07     ` Alec Warner
2013-02-13  1:15       ` Jeroen Roovers
2013-02-13  8:28         ` Fabian Groffen
2013-02-13 20:07 ` Agostino Sarubbo [this message]
2013-02-13 20:23   ` Peter Stuge
2013-02-13 20:31     ` Michael Weber
2013-02-13 20:34       ` Peter Stuge
2013-02-13 20:30   ` Michael Weber
2013-02-13 20:35     ` Michael Weber

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=1993687.8ZKES3KpCB@devil \
    --to=ago@gentoo.org \
    --cc=gentoo-dev@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