| View previous topic :: View next topic |
| Author |
Message |
nilbus
n00b
Joined: 19 Jan 2004
Posts: 28
Location: North Carolina State University
|
 Posted: Sun Feb 13, 2005 11:12 pm Post subject: PTY/TTY term probs w/ Screen & SSH on new install[fixed] |
 |
|
I just recently installed Gentoo on a new box, and I was having problems with Screen and SSH.
The root user could run screen and ssh, but none of the users could.
Screen would complain, "No more PTYs" "Sorry, could not find a PTY", and then exit.
SSH would complain, "Host key verification failed" anytime I tried to connect to another box as a user.
After searching the forums for a while, I found the solution that fixed both:
| Code: | | chmod 666 /dev/tty /dev/ptmx |
The /dev/tty, /dev/ptmx files on my other Gentoo boxes already had 666 (crw-rw-rw-) permissions, so I don't believe there is any security issue by setting these permissions.
I don't know if many other people are running into this, but hopefully it'll help! |
|
| Back to top |
|
 |
Chefpampel
n00b
Joined: 20 Oct 2004
Posts: 16
|
| Posted: Mon Feb 28, 2005 11:48 pm Post subject: |
|
|
I encountered the same issue and found this thread by google
http://www.networksecurityarchive.org/html/Secure-Shell/2004-11/msg00072.html
then I applied this to my gentoo-box (as root):
| Code: | | emerge udev; udevstart |
This worked for my box as well. Note: You don't have to edit udev.conf as described in the discussion linked to above.
Anybody knows if udevstart has to be called anytime the machine boots? Never used it before. |
|
| Back to top |
|
|
kimchi_sg
Advocate
Joined: 26 Nov 2004
Posts: 2968
|
| Posted: Sat Mar 12, 2005 11:19 am Post subject: Re: PTY/TTY term probs w/ Screen & SSH on new install[fi |
|
|
| nilbus wrote: | I found the solution that fixed both:
| Code: | | chmod 666 /dev/tty /dev/ptmx |
|
Thanks, that solved my screen problem too!  |
|
| Back to top |
|
|
Per Olav
n00b
Joined: 15 Sep 2004
Posts: 42
Location: Norway
|
| Posted: Mon Nov 28, 2005 9:37 pm Post subject: |
|
|
Solved mine too!
The error appeared after upgrading from 2.6.10 to 2.6.14.. I have no idea why |
|
| Back to top |
|
|
Nifty
n00b
Joined: 20 Aug 2004
Posts: 14
|
| Posted: Tue Nov 29, 2005 6:08 pm Post subject: |
|
|
| Per Olav wrote: | Solved mine too!
The error appeared after upgrading from 2.6.10 to 2.6.14.. I have no idea why |
I had excactly the same problem. |
|
| Back to top |
|
|
|
Documentation, Tips & Tricks
