public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Paulus <mark.paulus@wcom.com>
To: Corinna Vinschen <cygwin@cygwin.com>
Subject: Re: Authentication By-Pass Vulnerability in OpenSSH 2.3.1 (develsnapshot) (fwd)
Date: Mon, 12 Feb 2001 13:46:00 -0000	[thread overview]
Message-ID: <0G8N00K1EYX7YD@pmismtp04.wcomnet.com> (raw)
In-Reply-To: <20010209084018.C4880@cygbert.vinschen.de>

Do I need to do this, if I only use the ssh client??  I had a problem with 2.3.0p1,
where it wouldn't connect to my machine @ home through my Netgear
router/firewall.  However, the latest snapshot I downloaded allows me to
connect.  I don't want to back off and lose my ability to connect unless
you are going to kill me if I don't.    



On Fri, 09 Feb 2001 08:40:18 +0100, 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.!!!
>
>Corinna
>
>---------- Forwarded message ----------
>Date: Thu, 08 Feb 2001 18:15:00 -0500
>From: Niels Provos <provos@citi.umich.edu>
>To: security-announce@openbsd.org
>Subject: Authentication By-Pass Vulnerability in OpenSSH 2.3.1 (devel
>    snapshot)
>
>----------------------------------------------------------------------------
>
>                        OpenBSD Security Advisory
>
>                            February 8, 2001
>
>             Authentication By-Pass Vulnerability in OpenSSH-2.3.1
>
>----------------------------------------------------------------------------
>
>SYNOPSIS
>
>OpenSSH-2.3.1, a development snapshot, only checked if a public key
>for public key authentication was permitted.  In the protocol 2 part
>of the server, the challenge-response step that ensures that the
>connecting client is in possession of the corresponding private key
>has been omitted. As a result, anyone who could obtain the public key
>listed in the users authorized_keys file could log in as that user
>without authentication.
>
>A fix for this problem was committed on Februrary 8th.  The problem
>was introduced on January 18th.  This is a three week time window.
>
>----------------------------------------------------------------------------
>
>AFFECTED SYSTEMS
>
>This vulnerability affects only OpenSSH version 2.3.1 with support for
>protocol 2 enabled.  The latest official release OpenSSH 2.3.0 is not
>affected by this problem.  The latest snapshot version OpenSSH 2.3.2
>is not affected either.
>
>----------------------------------------------------------------------------
>
>RESOLUTION
>
>If you installed the OpenSSH 2.3.1 development snapshot, install the
>latest snapshot.  Currently, the latest snapshot is OpenSSH 2.3.2 which
>is available via http://www.openssh.com/ .
>
>----------------------------------------------------------------------------
>
>
>--
>Want to unsubscribe from this list?
>Check out: http://cygwin.com/ml/#unsubscribe-simple
>




--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2001-02-12 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 23:40 Authentication By-Pass Vulnerability in OpenSSH 2.3.1 (devel snapshot) (fwd) Corinna Vinschen
2001-02-09  0:14 ` Charles Wilson
2001-02-12  1:15   ` Corinna Vinschen
2001-02-12 13:46 ` Mark Paulus [this message]
2001-02-13  0:54   ` 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=0G8N00K1EYX7YD@pmismtp04.wcomnet.com \
    --to=mark.paulus@wcom.com \
    --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).