If I set my shell to "/bin/id -a" in /etc/passwd, I'm never able to log in successfully (I'm sure I typed my password correctly):

C:\cygwin\etc>ssh localhost
[EMAIL PROTECTED]'s password:
Permission denied, please try again.
[EMAIL PROTECTED]'s password:

If I set my shell to "/bin/id", I see this:

C:\cygwin\etc>ssh localhost
[EMAIL PROTECTED]'s password:
Last login: Tue Nov 14 12:09:47 2006 from 127.0.0.1
Fanfare!!!
You are successfully logged in to this server!!!
/bin/id: Permission denied
Connection to localhost closed.

I get "Permission denied" for /bin/sh as well, so it appears that I can't execute anything in the /bin directory when I try to connect with ssh.

Thanks for the suggestion. I'm pretty much out of ideas at this point. I've been using a Win2K system until recently, and I'm finding the whole issue of permissions in WinXP problematic.

Any other thoughts?

-B

Dave Korn wrote:
On 14 November 2006 18:30, Brian Kasper wrote:

Here's the text of my most recent login attempt:

 >kasper 509 $ ssh localhost
 >[EMAIL PROTECTED]'s password:
 >Warning: No xauth data; using fake authentication data for X11
 >forwarding.
 >Last login: Tue Nov 14 10:00:34 2006 from 127.0.0.1
 >Fanfare!!!
 >You are successfully logged in to this server!!!
 >/bin/bash: Permission denied
 >Connection to localhost closed.

working correctly.  The permissions on c:/cygwin/bin/bash.exe are ugo+rwx:

-rwxrwxrwx 1 kasper Users 467968 Nov  2 19:22 /bin/bash.exe

and I've given "full control" permission to "Everyone", "kasper", and
"sshd_server" for the entire c:/cygwin directory tree.

I'd really appreciate any pointers anyone can offer.

  Try replacing '/bin/bash' with /bin/id -a' in your /etc/passwd, and let's
see who cygwin thinks you are when you log in.  Then we can get into looking
at ACLs.

    cheers,
      DaveK


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Reply via email to