From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Taylan Kammer <taylan.kammer@gmail.com>
Cc: Maxime Devos <maximedevos@telenet.be>, guix-devel@gnu.org
Subject: Re: Commit pushed to master with unauthorised signature
Date: Thu, 11 Mar 2021 15:59:16 +0100 [thread overview]
Message-ID: <87im5xbut7.fsf@nckx> (raw)
In-Reply-To: <19be2417-8fc3-2b13-0a17-975fe0d5c1cc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
Taylan,
So if I needed to send you encrypted mail, I'd have to possess all
of your current GPG keys and encrypt to all of them? Thanks for
the heads-up ;-) I'm not sure if that's how GPG is supposed to
work (‘who does’, you say? fair point).
I do know that UIDs like ‘Jessie Doe (professional)’ are
discouraged because people signing your key would (according to
GPG logic) be vouching that you are, in fact, professional.
Anyway, you still need to make sure that *all* of your keys are
available on Savannah. It seems they are but they've expired.
Taylan Kammer 写道:
> I'm hopping workstations recently, and my general habit is to
> create new
> keys on each machine I'm using and register them where ever
> needed.
> (E.g. .ssh/authorized_keys on machines I access, GitHub account,
> etc.)
Makes good sense for SSH keys.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-03-11 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 21:22 Commit pushed to master with unauthorised signature Tobias Geerinckx-Rice
2021-03-10 23:15 ` Taylan Kammer
2021-03-11 7:37 ` Maxime Devos
2021-03-11 13:11 ` Taylan Kammer
2021-03-11 14:59 ` Tobias Geerinckx-Rice [this message]
2021-03-11 22:53 ` Taylan Kammer
2021-03-11 15:16 ` Julien Lepiller
2021-03-11 19:16 ` Leo Famulari
2021-03-11 23:02 ` Taylan Kammer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im5xbut7.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=taylan.kammer@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).