I actually have execute perms also...maybe that makes a difference? I found the issue using strace:
strace ssh host and it spews gibberish for a bit, then you see something like open (/dev/tty),??? ENOACCESS(-1,????) (sorry, from memory...) which indicated that my user couldn't access the device, since the error appeared shortly (in gibberish terms) before exit. The open was successful when the I ran ssh as root, which worked right anyway. good luck rick On Fri, 16 Feb 2001, Lance Levsen wrote: > > > where a regular user couldn't use ssh due to ' no controlling tty' > > That would have been me. > > > I found that the issue was an inability for nonroot to write to /dev/tty > > and changed o+w for /dev/tty > > No such luck on my end, /dev/tty is already 0666. > > Sorry, I can't answer your other questions. > > > thanks > > rick > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >