| 1 |
Hi, folks! |
| 2 |
|
| 3 |
I'm trying to get sshd working on an embryonic Gentoo installation on my |
| 4 |
laptop. The reason is that I want to ssh from my nice comfy desktop |
| 5 |
system into this laptop to do the rest of the installation stuff. |
| 6 |
|
| 7 |
The installation kernel with which I'm having problems is: |
| 8 |
Linux livecd 2.6.30-gentoo-r8 #1 SMP Tue Nov 3 11:40:51 UTC 2009. |
| 9 |
|
| 10 |
Having started sshd on my laptop, when I do |
| 11 |
|
| 12 |
ssh -lroot 192.168.2.101 |
| 13 |
|
| 14 |
from my desktop, I get prompted for my ssh key's pass phrase, which I |
| 15 |
enter. Thereafter, nothing happens, and it continues to happen for a |
| 16 |
long, long time. |
| 17 |
|
| 18 |
I've run sshd as sshd -d, which puts debugging info onto the screen. It |
| 19 |
turns out my system can't create a pty "pseudo terminal". Here is the |
| 20 |
debugging output. Please note the lines marked by "<=====": |
| 21 |
|
| 22 |
Postponed publickey for root from 192.168.2.100 port 41130 ssh2 |
| 23 |
debug1: userauth-request for user root service ssh-connection method |
| 24 |
publickey |
| 25 |
debug1: attempt 2 failures 0 |
| 26 |
debug1: temporarily_use_uid: 0/0 (e=0/0) |
| 27 |
debug1: trying public key file /root/.ssh/authorized_keys |
| 28 |
debug1: fd 4 clearing O_NONBLOCK |
| 29 |
debug1: matching key found: file /root/.ssh/authorized_keys, line 1 |
| 30 |
Found matching DSA key: a8:6a:76:30:f8:a4:4e:c4:3b:cd:ba:3d:20:87:0c:8f |
| 31 |
debug1: restore_uid: 0/0 |
| 32 |
debug1: ssh_dss_verify: signature correct |
| 33 |
debug1: do_pam_account: called |
| 34 |
Accepted publickey for root from 192.168.2.100 port 41130 ssh2 |
| 35 |
debug1: monitor_child_preauth: root has been authenticated by privileged |
| 36 |
process |
| 37 |
debug1: PAM: establishing credentials |
| 38 |
debug1: Entering interactive session for SSH2. |
| 39 |
debug1: server_init_dispatch_20 |
| 40 |
debug1: server_input_channel_open: ctype session rchan 0 win 65536 max |
| 41 |
16384 |
| 42 |
debug1: input_session_request |
| 43 |
debug1: channel 0: new [server-session] |
| 44 |
debug1: session_new: session 0 |
| 45 |
debug1: session_open: channel 0 |
| 46 |
debug1: session_open: session 0: link with channel 0 |
| 47 |
debug1: server_input_channel_open: confirm session |
| 48 |
debug1: server_input_channel_req: channel 0 request pty-req reply 0 |
| 49 |
debug1: session_by_channel: session 0 channel 0 |
| 50 |
debug1: session_input_channel_req: session 0 req pty-req |
| 51 |
debug1: Allocating pty. <========================== |
| 52 |
openpty: No such file or dIrectory <========================== |
| 53 |
session_pty_req: session 0 alloc failed <========================== |
| 54 |
debug1: server_input_channel_req: channel 0 request shell reply 0 |
| 55 |
debug1: session_by_channel: session 0 channel 0 |
| 56 |
debug1: session_input_channel_req: session 0 req shell |
| 57 |
debug1: Forced command (key option) '/bin/bash' |
| 58 |
Exiting on signal 2 |
| 59 |
debug1: do_cleanup |
| 60 |
debug1: PAM: cleanup |
| 61 |
debug1: PAM: deleting credentials |
| 62 |
debug1: PAM: closing session |
| 63 |
|
| 64 |
Clearly openpty (a C function) is failing to find some file. Don't you |
| 65 |
just love error messages like "No such file or directory" which forget |
| 66 |
to identify the filename? I'm guessing that the file it can't find is |
| 67 |
the device file for the new pty. |
| 68 |
|
| 69 |
Is there anything I can do to get sshd working from this kernel (and if |
| 70 |
so, what?), or is there something fundamentally wrong with the kernel |
| 71 |
configuration? |
| 72 |
|
| 73 |
Thanks in advance for any and all help! |
| 74 |
|
| 75 |
-- |
| 76 |
Alan Mackenzie (Nuremberg, Germany). |
Archives