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: <269620-22003112016515391@M2W095.mail2web.com> X-Priority: 3 Reply-To: lhall AT rfk DOT com X-Originating-IP: 209.113.174.244 From: "lhall AT pop DOT ma DOT ultranet DOT com" To: maxb AT ukf DOT net, rsiklos AT adexa DOT com, cygwin AT cygwin DOT com Subject: Re: accessing network shares through rlogin Date: Mon, 20 Jan 2003 11:51:53 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 X-OriginalArrivalTime: 20 Jan 2003 16:51:53.0014 (UTC) FILETIME=[3BCB3D60:01C2C0A4] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h0KGqAd20593 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? ;-) ) Larry Original Message: ----------------- From: Max Bowsher maxb AT ukf DOT net Date: Mon, 20 Jan 2003 16:30:24 -0000 To: lhall AT rfk DOT com, rsiklos AT adexa DOT com, cygwin AT cygwin DOT com Subject: Re: accessing network shares through rlogin lhall AT pop DOT ma DOT ultranet DOT com wrote: > Sounds like there's need for code inspection and a possible patch. Isn't the consensus that this is an unavoidable artefact of the way Windows authentication works? To summarize: rsh/ssh daemons run as SYSTEM, which has permission to hand out authentication tokens as it sees fit within the local machine, but since those tokens have no password info attached, they are no good for authenticating to other machines over the network. > That's the only idea I can offer that doesn't rely on allot of > conjecture (which would be of no value). No conjecture necessary? Or is my summary based on conjecture? > Absent that, the > suggestions you made are the > best "workarounds" for the current state. > > Larry > > Original Message: > ----------------- > From: Rob Siklos rsiklos AT adexa DOT com > Date: Mon, 20 Jan 2003 10:20:51 -0500 > To: cygwin AT cygwin DOT com > Subject: accessing network shares through rlogin > > > > The problem is that when I rlogin to a windows 2000 machine running > cygwin and a .rhosts file exists so I don't have to enter a password, > I can't access any other windows network shares from that rlogin > session. > > However, if I delete the .rhosts file (so I DO have to enter a > password), I can access shares just fine. If I connect using telnet, > I can also access network shares. > > The same situation exists when I use ssh: if it is set up so that I > have to enter my password, I can access shares. But if I use public > key pairs so that I don't have to enter my password, I can't access > any network shares. -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . -- 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/