DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:from:date:to:subject:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=tgE
	0nfv7EKRo50Rsg4MevXayPi1LNS0AfebKpv8QJdEZaW947sPuR2eHba0ug3PND0k
	i4cwADwXuymyPOIs55E3av+X5LPvC1GqO3hp3LAGVNMTR5Bmjy1wliQEMvu4I5hG
	vKXlSzg+Q/265qPPrJUs/GBpHQYgbxWA3ruSGUWU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <20160112220928.53666.qmail@sourceware.org>
From: root@sourceware.org
Date: Tue, 12 Jan 2016 22:09:28 +0000
To: cygwin@sourceware.org
Subject: sourceware/gcc ssh public key analysis
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Due to recent user reports of difficulty logging onto the server
known as sourceware.org / gcc.gnu.org / etc., we are scanning
your installed ssh public keys for continued compatibility.
Here is your analysis.

FILENAME /home/cygwin/.ssh/authorized_keys
FILEDATE 2015-02-06
SHELL you have shell access
RSA 2048: OK
RSA 2048: OK
RSA 2048: OK
RSA 4096: OK
RSA 2048: OK

You have at least one strong key: no further action is required.

Happy hacking!

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple