ssh unter cygwin: Problem bei Ausführung aus PHP

From: Neven Luetic (Neven.Luetic_at_hanse.net)
Date: 01/12/05 

Date: Wed, 12 Jan 2005 11:32:41 +0100

Hallo,

ich habe ein eigenartiges Problem:
ich will einigen Windowsusern eine php-Oberfläche zur
Datensicherung von Servern im Internet zur Verfügung stellen. Dabei
werden - per system() - ssh (von cygwin, mit keys ohne passphrase) und
rsync (ebenfalls die cygwin-version) verwendet.

Von einem Windowsrechner aus kann ich nun zwar in der Cygwinshell oder
der Eingabeaufforderung "ssh user@server befehl" erfolgreich eingeben,
versuche ich das gleiche aber aus PHP heraus, bleibt der ssh-Befehl
hängen. Als Server benutze ich den Apache (1.3.31, nicht Cygwin), der als
Service unter der Benutzerkennung des aktuell angemeldeten Benutzers
läuft.

Wenn ich das ganze lokal im Debugmodus durchführe erhalte ich folgende
Protokolle von Client und vom Server:

debug1: Connecting to xxx.xxx.xx [000.000.000.000] port 22.
debug1: Connection established.
debug1: identity file /home/xxx/.ssh/identity type -1
debug1: identity file /home/xxx/.ssh/id_rsa type 1
debug1: identity file /home/xxx/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.4p1
debug1: match: OpenSSH_3.4p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.9p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'xxx.xxx.xx' is known and matches the RSA host key.
debug1: Found key in /home/xxx/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/xxx/.ssh/identity
debug1: Offering public key: /home/xxx/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 149

Im Erfolgsfall, bei Ausführung von der Kommandozeile, geht dieses
Protokoll folgendermasßen weiter, bis zu diesem Punkt sind die Protokolle
identisch:
...
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending command: ls -lt
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0

Server:
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: private host key: #0 type 0 RSA1
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: read PEM private key done: type RSA
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: private host key: #1 type 1 RSA
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: read PEM private key done: type DSA
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: private host key: #2 type 2 DSA
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: inetd sockets after dupping: 3, 3
Jan 12 11:00:19 linuxpc sshd[9087]: Connection from ::ffff:xxx.xxx.xxx.xxx port 1047
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: Client protocol version 2.0; client software version OpenSSH_3.9p1
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: match: OpenSSH_3.9p1 pat OpenSSH*
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: Enabling compatibility mode for protocol 2.0
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: Local version string SSH-1.99-OpenSSH_3.9p1
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: PAM: initializing for "xxx"
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: PAM: setting PAM_RHOST to "xxxx.xxx"
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: PAM: setting PAM_TTY to "ssh"
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: temporarily_use_uid: 1000/100 (e=0/0)
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: trying public key file /home/xxx/.ssh/authorized_keys
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: matching key found: file /home/xxx/.ssh/authorized_keys, line 2
Jan 12 11:00:19 linuxpc sshd[9087]: Found matching RSA key: 72:50:97:a7:40:09:3b:77:0a:8d:43:59:fa:32:a7:02
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: restore_uid: 0/0
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: temporarily_use_uid: 1000/100 (e=0/0)
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: trying public key file /home/xxx/.ssh/authorized_keys
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: matching key found: file /home/xxx/.ssh/authorized_keys, line 2
Jan 12 11:00:19 linuxpc sshd[9087]: Found matching RSA key: 72:50:97:a7:40:09:3b:77:0a:8d:43:59:fa:32:a7:02
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: restore_uid: 0/0

im Erfolgsfall geht es so weiter:
...
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: ssh_rsa_verify: signature correct
Jan 12 11:00:19 linuxpc sshd[9087]: Accepted publickey for xxx from
::ffff:xxx.xxx.xxx.xxx port 1047 ssh2
Jan 12 11:00:19 linuxpc sshd[9087]: debug1: monitor_child_preauth: xxx has been authenticated by privileged process
Jan 12 11:00:19 linuxpc sshd[9089]: debug1: PAM: reinitializing credentials
Jan 12 11:00:19 linuxpc sshd[9089]: debug1: permanently_set_uid: 1000/100
Jan 12 11:00:19 linuxpc sshd[9089]: debug1: Entering interactive session for SSH2.
Jan 12 11:00:19 linuxpc sshd[9089]: debug1: server_init_dispatch_20
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: server_input_channel_open: ctype session rchan 0 win 131072 max 32768
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: input_session_request
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: channel 0: new [server-session]
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_new: init
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_new: session 0
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_open: channel 0
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_open: session 0: link with channel 0
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: server_input_channel_open: confirm session
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: server_input_channel_req: channel 0 request exec reply 0
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_by_channel: session 0 channel 0
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_input_channel_req: session 0 req exec
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: Received SIGCHLD.
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_by_pid: pid 9090
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_exit_message: session 0 channel 0 pid 9090
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_exit_message: release channel 0
Jan 12 11:00:21 linuxpc sshd[9089]: debug1: session_close: session 0 pid 9090
Jan 12 11:00:22 linuxpc sshd[9089]: debug1: channel 0: free: server-session, nchannels 1
Jan 12 11:00:22 linuxpc sshd[9089]: Connection closed by ::ffff:xxx.xxx.xxx.xxx
Jan 12 11:00:22 linuxpc sshd[9089]: debug1: do_cleanup
Jan 12 11:00:22 linuxpc sshd[9089]: debug1: PAM: cleanup
Jan 12 11:00:22 linuxpc sshd[9089]: Closing connection to ::ffff:xxx.xxx.xxx.xxx
Jan 12 11:00:22 linuxpc sshd[9089]: debug1: PAM: cleanup

Relevant Pages

  • Cant get authorized_keys to work
    ... My client machine is Windows 2000 Professional and the server ... I ran the cygwin shell by double-clicking the icon that it created ... Rhosts Authentication disabled, ... debug1: Connection established. ...
    (SSH)
  • Re: Kerberos machine authentication - apparent authentication fail
    ... > until logon), the wireless connection can kick off when it is ready. ... > was confirmed in the server event logs with IAS (i set that up as the radius ... > as an ordinary user kicks in and takes over from the machine authentication. ... > while the network sorts itself out and a double click on a network link of ...
    (microsoft.public.windows.server.security)
  • Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... SYSTEM account. ... In IIS I took the virtual server that I was testing, ... Authentication premise. ... From a website perspective, I ...
    (microsoft.public.inetserver.iis.security)
  • Need help configuring Wireless Connection profile
    ... I have an SBS 2003 server and a Server 2003 member server set up using RADIUS ... Windows authentication for all users,4129,LRG\ryanv,4149,Wireless WPA2 PEAP ... Certificate Services ...
    (microsoft.public.windowsxp.general)
  • Re: Remote Web Workplace Issues-Please help!
    ... Open the Server Management Console, ... client after Authentication" right. ... permissions, and Microsoft Windows user rights according to the KB 812614. ... Download the IIS Resource Kit tools from the following page: ...
    (microsoft.public.windows.server.sbs)