Mail Archives: cygwin/2003/01/20/11:30:36
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.
--
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/
- Raw text -