From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20207 invoked by alias); 14 Feb 2016 01:37:36 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 20194 invoked by uid 89); 14 Feb 2016 01:37:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.3 required=5.0 tests=AWL,BAYES_40,CYGWIN_OWNER_BODY,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:1111, H*i:sk:CACoZoo, H*i:Wh9a8CDvyUHpqj5, H*f:sk:Br5xYFv X-HELO: resqmta-po-07v.sys.comcast.net Received: from resqmta-po-07v.sys.comcast.net (HELO resqmta-po-07v.sys.comcast.net) (96.114.154.166) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Sun, 14 Feb 2016 01:37:34 +0000 Received: from resomta-po-14v.sys.comcast.net ([96.114.154.238]) by resqmta-po-07v.sys.comcast.net with comcast id J1dQ1s00358ss0Y011dYrC; Sun, 14 Feb 2016 01:37:32 +0000 Received: from HOME1 ([24.18.54.164]) by resomta-po-14v.sys.comcast.net with comcast id J1dY1s00M3YafjL011dYgm; Sun, 14 Feb 2016 01:37:32 +0000 Reply-To: From: "David Willis" To: References: <019c01d163bc$fe2fc500$fa8f4f00$@comcast.net> <019e01d163c2$d678c7e0$836a57a0$@comcast.net> <023901d165e4$925507d0$b6ff1770$@comcast.net> <87d1s1c8ld.fsf@Rainer.invalid> In-Reply-To: Subject: RE: Possible Security Hole in SSHD w/ CYGWIN? Date: Sun, 14 Feb 2016 01:37:00 -0000 Message-ID: <025801d166c8$462642e0$d272c8a0$@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00207.txt.bz2 Also, just wanted to respond to this one piece of the message to clarify - The only change I made to what ssh_host_config does is to use the existing domain admin account cyg_server rather than creating a new local admin account (and it actually detects it automatically if it exists already so this isn't even really doing anything different) -----Original Message----- From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of Erik Soderquist Sent: Saturday, February 13, 2016 4:14 PM To: cygwin@cygwin.com Subject: Re: Possible Security Hole in SSHD w/ CYGWIN? > I don't know how you've arrived at the setup you just described, but > it's not the one that sshd_host_config produces. Yes, setting up an > SSHD wrongly can open up security holes, no surprise here. Once again, assumptions. While I can't explicitly vouch for David's environment, as I do not have access to check, I can vouch for mine, and mine was configured using sshd_host_config, with the only changes after sshd_host_config being regarding TCP and X tunneling. --- Erik -- 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