Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 20 Jan 2003 17:58:40 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: accessing network shares through rlogin Message-ID: <20030120165840.GF29236@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <269620-22003112016515391@M2W095.mail2web.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <269620-22003112016515391@M2W095.mail2web.com> User-Agent: Mutt/1.4i On Mon, Jan 20, 2003 at 11:51:53AM -0500, lhall@pop.ma.ultranet.com wrote: > Right. Windows authetication is the main hinderance. > However, as the poster pointed out, if you're forced to > enter your password (by the lack of a .rhosts file for an > rsh session), then Windows password authentication > occurs and shares are available. But I guess I should > clarify the difference I see and the reason for my response. > While key authentication (via ssh) can't provide the password > protected share access, rsh access (with a .rhosts) should be > able to based on the posters description. That's the part > that I think could benefit from closer inspection. Huh? I don't understand what you're trying to say. If rhosts authentication takes place... how should Cygwin be able to create a token with network credentials??? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/