Re: ssh and devices

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

Re: ssh and devices

> 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

Re: ssh and devices

To quote Rick Rezinas <[EMAIL PROTECTED]>, # Hi, # # I'm using testing # I was having an issue (think I saw a post regarding this recently), # where a regular user couldn't use ssh due to ' no controlling tty' # # I found that the issue was an inability for nonroot to write to /dev/tty # and chan

ssh and devices

Hi, I'm using testing I was having an issue (think I saw a post regarding this recently), where a regular user couldn't use ssh due to ' no controlling tty' I found that the issue was an inability for nonroot to write to /dev/tty and changed o+w for /dev/tty Now all seems happy, but I was curiou