From: Charles Wilson <cwilson@ece.gatech.edu>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: Authentication By-Pass Vulnerability in OpenSSH 2.3.1 (devel snapshot) (fwd)
Date: Fri, 09 Feb 2001 00:14:00 -0000 [thread overview]
Message-ID: <3A83A7B3.756449B5@ece.gatech.edu> (raw)
In-Reply-To: <20010209084018.C4880@cygbert.vinschen.de>
Corinna Vinschen wrote:
> FYI for those running snapshots. I have removed the openssh-20010202
> snapshot from cygwin/latest.
>
> If you are using the openssh-20010202 snapshot PLEASE REVERT BACK TO
> openssh-20001221 OR openssh-2.3.0p1.!!!
This means you have to re-regenerate your RSA keys after reverting back
to the older version, right?
--Chuck
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2001-02-09 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 23:40 Corinna Vinschen
2001-02-09 0:14 ` Charles Wilson [this message]
2001-02-12 1:15 ` Corinna Vinschen
2001-02-12 13:46 ` Authentication By-Pass Vulnerability in OpenSSH 2.3.1 (develsnapshot) (fwd) Mark Paulus
2001-02-13 0:54 ` Authentication By-Pass Vulnerability in OpenSSH 2.3.1 (devel snapshot) (fwd) Corinna Vinschen
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=3A83A7B3.756449B5@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@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).