From: "Schulman, Andrew via cygwin-apps" <cygwin-apps@cygwin.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: RE: updated SSH key
Date: Thu, 20 Feb 2020 21:35:00 -0000 [thread overview]
Message-ID: <DM6PR09MB449552768A9D2B3E0594954CF8130@DM6PR09MB4495.namprd09.prod.outlook.com> (raw)
In-Reply-To: <36c88d41-549b-8bfc-7386-49ba40538e3f@dronecode.org.uk>
Thanks!
I was just sitting here thinking about the merits of verifying a new key request like that by some kind of secure signature system, versus just posting the request on a public mailing list, and having a human acknowledge to the developer's previously known email address. I have to say, I can't see much more security benefit from the first method, that would justify the extra hassle. The second method is pleasantly simple.
Andrew E. Schulman
Office of Compliance
U.S. Environmental Protection Agency
202-564-5244
-----Original Message-----
From: Jon Turney <jon.turney@dronecode.org.uk>
Sent: Thursday, February 20, 2020 4:32 PM
To: cygwin-apps@cygwin.com
Cc: Schulman, Andrew <Schulman.Andrew@epa.gov>
Subject: Re: updated SSH key
On 20/02/2020 19:37, Andrew Schulman via cygwin-apps wrote:
> Name: Andrew Schulman
Done.
next prev parent reply other threads:[~2020-02-20 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 19:38 Andrew Schulman via cygwin-apps
2020-02-20 21:31 ` Jon Turney
2020-02-20 21:35 ` Schulman, Andrew via cygwin-apps [this message]
2020-02-21 15:20 ` Jon Turney
-- strict thread matches above, loose matches on Subject: below --
2021-10-12 17:09 updated ssh key Andrew Schulman
2021-10-12 19:34 ` Jon Turney
2021-10-12 19:43 ` Andrew Schulman
2018-10-24 23:37 Andrew Schulman
2018-10-25 10:39 ` Jon Turney
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=DM6PR09MB449552768A9D2B3E0594954CF8130@DM6PR09MB4495.namprd09.prod.outlook.com \
--to=cygwin-apps@cygwin.com \
--cc=Schulman.Andrew@epa.gov \
--cc=jon.turney@dronecode.org.uk \
/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).