From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygwin.com sftp key fingerprint?
Date: Mon, 01 Jun 2015 16:41:00 -0000 [thread overview]
Message-ID: <20150601164131.GR4308@calimero.vinschen.de> (raw)
In-Reply-To: <87lhg3l7wr.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Jun 1 18:17, Achim Gratz wrote:
> Andrew Schulman writes:
> > OK, here you go. The patch is a bit large, because I took the opportunity to
> > reorganize the text a bit and add a new section showing how to upload packages
> > the automated way using cygport up. The complete revised page is at
> > http://home.comcast.net/~andrex2/cygwin/package-upload.html .
>
> Looks good. However, you still haven't verified the fingerprint(s) with
> Sourceware Overseers or did you? That I'm getting the same fingerprint
> as you is a good sign, but certainly not a confirmation.
Running your commands on sourceware itself shows the exact same
results when accessing the public host RSA key:
$ ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub
1024 1d:1e:46:7f:4d:73:8d:10:20:c3:4c:5a:34:14:44:23 /etc/ssh/ssh_host_rsa_key.pub (RSA)
$ awk '{print $2}' /etc/ssh/ssh_host_rsa_key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64
MFNiczzfX8/nvLSRZwR3CxMyycKtMan64Zm4C373FeM=
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-06-01 16:41 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
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 [this message]
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=20150601164131.GR4308@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).