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
Message-ID: <00da01c2336a$b940b210$0100a8c0@wdg.uk.ibm.com>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <bkeener AT thesoftwaresource DOT com>, <cygwin AT cygwin DOT com>
References: <VA DOT 00000c0e DOT 002c0d59 AT thesoftwaresource DOT com> <20020724163138 DOT F3921 AT cygbert DOT vinschen DOT de> <VA DOT 00000c10 DOT 00aec8ba AT thesoftwaresource DOT com> <20020724201757 DOT GC21112 AT redhat DOT com> <VA DOT 00000c11 DOT 0214eedd AT thesoftwaresource DOT com>
Subject: Re: W2K and sshd, ssh  - asks for password
Date: Thu, 25 Jul 2002 00:34:58 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Brian Keener wrote:
> You are 100% right in both cases - Had Corinna not pointed it out, I
> know you would have and cygwin-apps was not the appropriate place to
> post.  At the time I wrote it, cygwin-apps seemed appropriate (in my
> mind) but I should have gone to the web and reread the description of
> what goes in cygwin-apps versus cygwin.  I was wrong in my choice.

OK, no ones memory is perfect (mine just being plain strange - I can tell you
the registration numbers of all the series-leading ships in Star Trek, bu won't
necessarily know what day it is :-) )

Lets continue on cygwin@

>> Max Bowsher wrote:
>> Why the lousy attitude?
>
> The lousy attitude stems from the fact that I sometimes feel the
> responses (not just to me) are sometimes a bit more terse than need
> me.

True. I think that the sheer volume of Cygwin mail reduces tolerance levels
somewhat.

...snip...
> As to the rest of Max's comments:
>
>> 1. Corinna was entirely justified - your question has no place on
>> cygwin-apps
>
>  Correct.  As I said previously it was not the lesson but the method
> of teaching.

I agree, as above.

>> 2. The Red Hat people on the lists are usually very busy. Be kind to
>> them.
>
> Yes they are - I am immensly impressed by them and their talents.

Definitely - me too!

> Would that I could program as well and tackle some of the projects
> and problems they do.

Ditto :-)

>> 3. Just because Corinna may be the person you think is most
>> qualified to help you, don't assume that no one else can. Now, I had
>> a similar problem, which I
>
> Again Max is correct - I was sure others could help but I was also
> sure Corinna was a prime candidate for recognizing what was wrong
> (besides the wrong newsgroup :-) )  I am glad I was able to jog Max's
> memory on his problem and also that he has offered to help me on mine.
>
> I will attempt the steps Max describes later this evening or tomorrow
> and post the results as requested (to the Cygwin list).

For the record, at least part of the problem was a CYGWIN=ntsec foulup. I'd
intended to enter it in the system env vars box, but had actually put it in the
user env vars box. Ooops!

> As to the discussion of ntsec being required and whether or not NTFS
> was or was not required - I thought I remembered reading that NTFS
> was a requirement for ntsec to work and therefore if sshd and the
> authentication require ntsec then they would also require NTFS?

I think that only the POSIX file mode using ACLs requires NTFS. The rest of what
ntsec does just requires an NT OS, and FAT will do.

Max.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/