public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@vinschen.de>
To: Prentis Brooks <prentis@aol.net>
Cc: Cygwin <cygwin@sourceware.cygnus.com>
Subject: [ANNOUNCEMENT]: patched openSSH-1.2.2 [was Re: No this has a nasty bite]
Date: Sat, 27 May 2000 14:35:00 -0000	[thread overview]
Message-ID: <39303F67.D6C4E256@vinschen.de> (raw)
In-Reply-To: <NEBBLEPLMLJEEFHAGMDMMECJCAAA.prentis@aol.net>

Prentis Brooks wrote:
> You have RSA Authentication enabled and running as user foo on port 22.  You
> have another Daemon running SSH with password authentication on port 26.  If
> user bar sets up RSA keys in his/her home directory and then connects to
> port 22, it will authenticate him/her via the keys in bar's home directory
> and then promptly drop them to the shell as foo... this is bad.

Should be solved in my new version. You will find it in

ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Vinschen_Corinna/V1.1.1

files

	openssh-1.2.2-2.README
	openssh-1.2.2-2.tar.gz
	openssh-1.2.2-2.diff


Have fun,
Corinna

-- 
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-05-27 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-26 10:45 No this has a nasty bite Prentis Brooks
2000-05-27 14:35 ` Corinna Vinschen [this message]
2000-05-27 20:58   ` [ANNOUNCEMENT]: patched openSSH-1.2.2 [was Re: No this has a nasty bite] Prentis Brooks
2000-05-28  2:52     ` Corinna Vinschen
2000-05-30 11:19       ` Prentis Brooks
2000-05-30 12:20         ` Corinna Vinschen
     [not found] <s048jsc0d8a3j88k2r57mkkbs21qbac6jo@4ax.com>
2000-05-30 12:11 ` Prentis Brooks

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=39303F67.D6C4E256@vinschen.de \
    --to=corinna@vinschen.de \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=prentis@aol.net \
    /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).