Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.0.1.1.0.20040127105458.0382a260@127.0.0.1>
X-Sender: 
Date: Tue, 27 Jan 2004 11:03:57 -0500
To: cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: ssh configuration that is pulling my hair out!
In-Reply-To: <40161B3C.C3F3D066@dessent.net>
References: <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040126123546 DOT 03cde5b0 AT 127 DOT 0 DOT 0 DOT 1> <NUTMEG8NYpyBnSrurDf00000017 AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <20040126184150 DOT GC15847 AT redhat DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040126140514 DOT 03d08fa8 AT 127 DOT 0 DOT 0 DOT 1> <40161B3C DOT C3F3D066 AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 03:03 AM 1/27/2004, Brian Dessent you wrote:
>Larry Hall wrote:
>
>> Precisely.  The idea of adding to the  FAQ for something that should be
>> obvious goes against my grain but I'm OK with the notion if doing so
>> addresses a problem.  But, at least to me, this one seems way off to one
>> end of "obviousness" so I have to question the "obvious" solution too.
>> Maybe there's a better solution because the problem isn't what we think
>> it is.
>
>While I understand that Cygwin cannot be responsible for what third
>parties say about its configuration, it shouldn't be entirely mysterious
>why a lot of people see that site first, and then ask here.  If you
>google for "cygwin sshd configuration" the first four hits are on
>erdelynet.com.  I don't think it's that outrageous that someone would
>google first, try the instructions presented in the results, and then
>seek out the official mailing list when that doesn't work.  Or, in other
>words, "Cygwin is cygwin, why should it matter where I saw the
>instructions?"  I don't think it would be wasteful to add a simple FAQ
>entry along the lines of "Q: I'm having problems with my sshd
>configuration, can you help?  A: Yes, please read
>/usr/share/doc/Cygwin/sshd.README.  Only those instructions are
>supported on the mailing list, if you still need help."



To me, that suggests that we need to either have a way to optionally 
start the configuration of packages from setup.exe and/or somehow queue
the user into the READMEs.  This is a bit more involved to implement 
than additions to the FAQ but it seems to me that it's much more likely 
to eliminate the questions on this and other package configuration issues 
that stem from 3rd party configuration advice.  But can anyone who has 
configured sshd using erdelynet.com, for example, confirm that this is the 
approach they took?



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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