updated ssh key

updated ssh key

[Andrew Schulman]

Name: Andrew Schulman
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "384-bit ECDSA, created by Andrew Schulman"
AAAAE2VjZHNhLXNoYTItbmlzdHAzODQAAAAIbmlzdHAzODQAAABhBIh5WtQRqhzLyhiCds
BhExlJjXY+NeKxt7tp3l4ViEOwGAPmiMp9keikNzVrpBy2poorumkZDCJrCxx3855UxdnV
E51GAO7toxiCMM8BNHX3fnDj6rgydpjCNRStBQUqWQ==
---- END SSH2 PUBLIC KEY ----

Re: updated ssh key

[Jon Turney]

On 12/10/2021 18:09, Andrew Schulman via Cygwin-apps wrote:
> Name: Andrew Schulman
> ---- BEGIN SSH2 PUBLIC KEY ----
> Comment: "384-bit ECDSA, created by Andrew Schulman"
> AAAAE2VjZHNhLXNoYTItbmlzdHAzODQAAAAIbmlzdHAzODQAAABhBIh5WtQRqhzLyhiCds
> BhExlJjXY+NeKxt7tp3l4ViEOwGAPmiMp9keikNzVrpBy2poorumkZDCJrCxx3855UxdnV
> E51GAO7toxiCMM8BNHX3fnDj6rgydpjCNRStBQUqWQ==
> ---- END SSH2 PUBLIC KEY ----

I ran my script to update your key, but it didn't seem to do anything, 
which confused me, until I noticed this appears to be the same as your 
current key [1].

[1] https://cygwin.com/pipermail/cygwin-apps/2020-February/039822.html

Re: updated ssh key

[Andrew Schulman]

> I ran my script to update your key, but it didn't seem to do anything, 
> which confused me, until I noticed this appears to be the same as your 
> current key [1].
> 
> [1] https://cygwin.com/pipermail/cygwin-apps/2020-February/039822.html

Doh. Thanks.

updated SSH key

[Andrew Schulman via cygwin-apps]

Name: Andrew Schulman
Package: screen
---- BEGIN SSH2 PUBLIC KEY ----
AAAAE2VjZHNhLXNoYTItbmlzdHAzODQAAAAIbmlzdHAzODQAAABhBIh5WtQRqhzLyhiCds
BhExlJjXY+NeKxt7tp3l4ViEOwGAPmiMp9keikNzVrpBy2poorumkZDCJrCxx3855UxdnV
E51GAO7toxiCMM8BNHX3fnDj6rgydpjCNRStBQUqWQ==
---- END SSH2 PUBLIC KEY ----

Re: updated SSH key

[Jon Turney]

On 20/02/2020 19:37, Andrew Schulman via cygwin-apps wrote:
> Name: Andrew Schulman

Done.

RE: updated SSH key

[Schulman, Andrew via cygwin-apps]

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.

Re: updated SSH key

[Jon Turney]

On 20/02/2020 21:35, Schulman, Andrew via cygwin-apps wrote:
> 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.

Yeah, it would be nice to have something like SSKM [1], but our gitolite 
usage is sufficiently non-standard that would need some hacking on to fit.

And that doesn't help with initial keys, and people who've lost their 
key (who we're presumably going to trust an email from), so given the 
small number of keys we're dealing with, it's hard to see it's worth the 
effort.

[1] https://gitolite.com/gitolite/contrib/sskm.html

updated ssh key

[Andrew Schulman]

Name: Andrew Schulman
Package: screen
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "2048-bit RSA, converted from OpenSSH"
AAAAB3NzaC1yc2EAAAADAQABAAABAQDJHwg85y9fnaw7qYzRF32vmwY2GW5Bwcgc/hOxsG
AWrpQJ9wsfFK5yHUmQnTmyyuttXhrOjrGsrUK1vtv59bFdJwsbh/i3jwnajBConXZwo3lU
rMBnqn5rXTiG/TM4zX18qPErvuKci4/KvDK6b3LG/byo80PrX7r4u50XVgCIAUsdCKIFSQ
kMh4rg/WWesXroFUZVFv3MooYpQ4kxrOgyan/uaVJU9+YYQPYFYYCUQteONzqiUty2Dp1/
JRpbsl9Gukcjy0GVN4bSSm96gtiGcUM6LnzIhD1UvKbvuAtjRGkqTm7OTjHVIV8xRcOtdH
OUjN751mQnb7IwJPWfcFuv
---- END SSH2 PUBLIC KEY ----

Re: updated ssh key

[Jon Turney]

On 25/10/2018 00:37, Andrew Schulman wrote:
> Name: Andrew Schulman
> Package: screen
> ---- BEGIN SSH2 PUBLIC KEY ----

I've updated your key for uploads (connecting as cygwin@cygwin.com)

I cannot update the key for your shell account on sourceware.  Follow 
the procedure at [1] (if you still have your old key, or contact 
overseers to get it changed)

[1] https://sourceware.org/sourceware/accountinfo.html