public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nicholas Jones <carpaski@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Manifest signing advice: use gpg-agent!
Date: Sun, 5 Sep 2004 03:20:36 -0400	[thread overview]
Message-ID: <20040905072036.GA7680@twobit.net> (raw)
In-Reply-To: <20040904222506.GA7667@pohl.lj.net>

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

> people putting their passphrase into the commit message.

Ummmm... How exactly? The commit message isn't prompted if
you are using repoman. You get one prompt _before_ your
passphrase comes up. If you're doing that, then you really
need to slow down.

If you _DO_ manage to do this, be sure to invalidate your
keys and pass the new fingerprint onto devrel.

If there is an issue here that you feel can be resolved by
a different kind of prompt, please let dev-portage know via
a bug and we can get on it.

--NJ


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-05  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04 22:34 [gentoo-dev] Manifest signing advice: use gpg-agent! Tom Martin
2004-09-05  7:20 ` Nicholas Jones [this message]
2004-09-05  9:22 ` Robin H. Johnson
2004-09-07  0:32 ` Mike Frysinger

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=20040905072036.GA7680@twobit.net \
    --to=carpaski@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