From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygwin.com sftp key fingerprint?
Date: Sun, 31 May 2015 10:24:00 -0000 [thread overview]
Message-ID: <20150531102439.GC4329@calimero.vinschen.de> (raw)
In-Reply-To: <87eglxkyjq.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On May 31 09:15, Achim Gratz wrote:
> Andrew Schulman writes:
> > I show the SFTP key fingerprint for cygwin.com as
> >
> > SHA256:MFNiczzfX8/nvLSRZwR3CxMyycKtMan64Zm4C373FeM
> >
> > Can anyone please confirm that?
>
> > ssh-keygen -lvf cygwin.com.pub
> 1024 1d:1e:46:7f:4d:73:8d:10:20:c3:4c:5a:34:14:44:23 [MD5] cygwin.com (RSA)
> +--[ RSA 1024]----+
> | EO&.o.oo o+|
> | +o* . .o+|
> | . + . . .|
> | + o . |
> | S o |
> | |
> | |
> | |
> | |
> +--[MD5]----------+
> > awk '{print $3}' cygwin.com.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64
> MFNiczzfX8/nvLSRZwR3CxMyycKtMan64Zm4C373FeM=
>
> > Is the key fingerprint posted anywhere on cygwin.com or sourceware.org? I can't
> > find it. If not, would someone mind adding it to the "Uploading Packages to
> > cygwin.com" page (https://sourceware.org/cygwin-apps/package-upload.html), so
> > people can verify it?
>
> Good idea.
PGA?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-31 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 22:06 Andrew Schulman
2015-05-31 7:15 ` Achim Gratz
2015-05-31 10:24 ` Corinna Vinschen [this message]
2015-05-31 21:08 ` Andrew Schulman
2015-06-01 8:50 ` Corinna Vinschen
2015-06-01 16:18 ` Achim Gratz
2015-06-01 16:41 ` Corinna Vinschen
2015-06-01 17:46 ` Achim Gratz
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=20150531102439.GC4329@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.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.
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).