Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <014401c2c0a4$e54acf90$78d96f83@pomello> From: "Max Bowsher" To: , , References: <269620-22003112016515391 AT M2W095 DOT mail2web DOT com> Subject: Re: accessing network shares through rlogin Date: Mon, 20 Jan 2003 16:56:37 -0000 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.2800.1106 lhall AT pop DOT ma DOT ultranet DOT 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. > > Sorry if I was a little vague initially (am I less so now? ;-) ) Umm? How is ssh key access different from rsh .rhosts access? They are both just a priviledged process deciding that a login is authorized hrough their own means, and telling Cygwin/Windows to let them in. Aren't they? 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/