堆棧內存溢出
  簡體   English   中英

使用Node.js ssh2模塊模擬ssh的ProxyCommand

[英]Emulating ssh's ProxyCommand using the Node.js ssh2 module

 原文  2014-03-04 14:11:42  1   1    node.js/ ssh

問題描述

我有一個服務器（例如，內置服務器），只能從另一台服務器（比如說，outerserver）到達，而不是運行節點服務器的服務器。 但是，節點服務器可以到達外部。 從命令行使用ssh時，我可以使用ProxyCommand配置文件語句來簡化連接。 我的配置文件如下所示： 

Host innerserver
ProxyCommand ssh outerserver nc innerserver 22

這允許我簡單地輸入ssh innerserver ，ssh將通過outerserver進行隧道傳輸。 現在我想用Node的ssh2模塊實現同樣的功能。 在文檔中，它說socks -option連接可用於“連接跳躍”，但它從未說明具體含義或如何使用它。 我嘗試了以下方法： 

var ssh2 = require('ssh2');
function runCommand(command, callback) {
  var connection = new ssh2();
  require('fs').readFile('/path/to/key/file', function(err, privateKey) {
    connection
      .on('ready', function() {
        connection.exec('nc innerserver 22', function(err, stream) {
          var innerConnection = new ssh2();
          innerConnection
            .on('ready', function() {
              innerConnection.exec(command, function(err, innerstream) {
                var data = '';
                innerstream.on('data', function(chunk) {
                  data += chunk;
                });
                innerstream.on('end', function() {
                  callback(data);
                });
              });
              console.log('ready');
            })
            .on('error', function(msg) {
              console.log('inner error:', msg);
              callback('error');
            })
            .connect({username:'user', privateKey: privateKey, sock:stream, debug: function(msg) {
              console.log('inner', msg);
            }});
        });
      })
      .on('error', function(msg) {
        console.log('outer error', msg);
        callback('error');
      })
      .connect({host:'outerserver', username:'user', privateKey:privateKey, debug: function(msg) {
        console.log('outer:', msg);
      }});    
  });
}

我得到以下輸出： 

outer: DEBUG: Parser: STATE_INIT
outer: DEBUG: Parser: STATE_GREETING
outer: DEBUG: Parser: STATE_HEADER
outer: DEBUG: Connection: Server ident: 'SSH-2.0-OpenSSH_6.4'
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 8)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: pktLen:1532,padLen:7,remainLen:1528
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: KEXINIT
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 8)
outer: DEBUG: Connection: Sent KEXINIT
outer: DEBUG: Connection: Comparing KEXInits...
outer: DEBUG: (local) Server->Client ciphers: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,blowfish-cbc,3des-cbc,arcfour256,arcfour128,cast128-cbc,arcfour
outer: DEBUG: (remote) Server->Client ciphers: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
outer: DEBUG: Connection: Server->Client Cipher: aes256-ctr
outer: DEBUG: (local) Client->Server ciphers: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,blowfish-cbc,3des-cbc,arcfour256,arcfour128,cast128-cbc,arcfour
outer: DEBUG: (remote) Client->Server ciphers: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
outer: DEBUG: Connection: Client->Server Cipher: aes256-ctr
outer: DEBUG: (local) KEX algorithms: diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
outer: DEBUG: (remote) KEX algorithms: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
outer: DEBUG: Connection: KEX: diffie-hellman-group14-sha1
outer: DEBUG: (local) Client->Server HMAC algorithms: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-sha1-96,hmac-md5-96
outer: DEBUG: (remote) Client->Server HMAC algorithms: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
outer: DEBUG: Connection: Client->Server HMAC: hmac-md5
outer: DEBUG: (local) Server->Client HMAC algorithms: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-sha1-96,hmac-md5-96
outer: DEBUG: (remote) Server->Client HMAC algorithms: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
outer: DEBUG: Connection: Server->Client HMAC: hmac-md5
outer: DEBUG: (local) Client->Server compression algorithms: none
outer: DEBUG: (remote) Client->Server compression algorithms: none,zlib@openssh.com
outer: DEBUG: Connection: Client->Server Compression: none
outer: DEBUG: (local) Server->Client compression algorithms: none
outer: DEBUG: (remote) Server->Client compression algorithms: none,zlib@openssh.com
outer: DEBUG: Connection: Server->Client Compression: none
outer: DEBUG: (local) Host key formats: ssh-rsa,ssh-dss
outer: DEBUG: (remote) Host key formats: ssh-rsa,ecdsa-sha2-nistp256
outer: DEBUG: Connection: Host key format: ssh-rsa
outer: DEBUG: Connection: Sent KEXDH_INIT
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: pktLen:828,padLen:7,remainLen:824
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: KEXDH_REPLY
outer: DEBUG: Connection: Checking host key format
outer: DEBUG: Connection: Checking signature format
outer: DEBUG: Connection: Verifying signature
outer: DEBUG: Connection: Sent NEWKEYS
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 8)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: pktLen:12,padLen:10,remainLen:8
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: NEWKEYS
outer: DEBUG: Connection: Sent SERVICE_REQUEST
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: pktLen:28,padLen:10,remainLen:16
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: hmacSize:16
outer: DEBUG: Parser: STATE_PACKETDATAVERIFY
outer: DEBUG: Parser: Verifying MAC
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: SERVICE_ACCEPT
outer: DEBUG: Connection: Sent USERAUTH_REQUEST (publickey -- check)
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: pktLen:300,padLen:4,remainLen:288
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: hmacSize:16
outer: DEBUG: Parser: STATE_PACKETDATAVERIFY
outer: DEBUG: Parser: Verifying MAC
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: USERAUTH_PK_OK
outer: DEBUG: Connection: Sent USERAUTH_REQUEST (publickey)
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: pktLen:12,padLen:10,remainLen:0
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: hmacSize:16
outer: DEBUG: Parser: STATE_PACKETDATAVERIFY
outer: DEBUG: Parser: Verifying MAC
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: USERAUTH_SUCCESS
outer: DEBUG: Connection: Sent CHANNEL_OPEN
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: pktLen:28,padLen:10,remainLen:16
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: hmacSize:16
outer: DEBUG: Parser: STATE_PACKETDATAVERIFY
outer: DEBUG: Parser: Verifying MAC
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: CHANNEL_OPEN_CONFIRMATION
outer: DEBUG: Channel: Sent CHANNEL_REQUEST (exec)
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: pktLen:28,padLen:18,remainLen:16
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: hmacSize:16
outer: DEBUG: Parser: STATE_PACKETDATAVERIFY
outer: DEBUG: Parser: Verifying MAC
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: CHANNEL_WINDOW_ADJUST
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: pktLen:12,padLen:6,remainLen:0
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: hmacSize:16
outer: DEBUG: Parser: STATE_PACKETDATAVERIFY
outer: DEBUG: Parser: Verifying MAC
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: CHANNEL_SUCCESS
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
outer: DEBUG: Parser: STATE_PACKET
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: pktLen:44,padLen:13,remainLen:32
outer: DEBUG: Parser: STATE_PACKETDATA
outer: DEBUG: Parser: Decrypting
outer: DEBUG: Parser: hmacSize:16
outer: DEBUG: Parser: STATE_PACKETDATAVERIFY
outer: DEBUG: Parser: Verifying MAC
outer: DEBUG: Parser: STATE_PACKETDATAAFTER, packet: CHANNEL_DATA
inner DEBUG: Parser: STATE_INIT
inner DEBUG: Parser: STATE_GREETING
inner DEBUG: Parser: STATE_HEADER
inner DEBUG: Connection: Server ident: 'SSH-2.0-OpenSSH_6.4'
inner DEBUG: Parser: STATE_PACKETBEFORE (expecting 8)
outer: DEBUG: Parser: STATE_PACKETBEFORE (expecting 16)
inner DEBUG: Connection: Sent KEXINIT

似乎內部聯系從未真正建立起來。 我究竟做錯了什么？

1 個解決方案

解決方案1
 9 已采納  2014-03-04 16:59:23

更新：您可能最好使用connection.forwardOut() （只要服務器允許），而不是依靠netcat或類似的實用程序來進行下一跳。

從ssh2 v0.2.19開始，你可以為連接跳轉做這樣的事情： 

var Connection = require('ssh2');

var conn1 = new Connection(),
    conn2 = new Connection();

conn1.on('ready', function() {
  console.log('FIRST :: connection ready');
  conn1.exec('nc 192.168.1.2 22', function(err, stream) {
    if (err) return console.log('FIRST :: exec error: ' + err);
    conn2.connect({
      sock: stream,
      username: 'user2',
      password: 'password2'
    });
  });
});
conn1.connect({
  host: '192.168.1.1',
  username: 'user1',
  password: 'password1'
});

conn2.on('ready', function() {
  console.log('SECOND :: connection ready');
  conn2.exec('uptime', function(err, stream) {
    if (err) return console.log('SECOND :: exec error: ' + err);
    stream.on('data', function(data) {
      console.log(data.toString());
    });
    stream.on('end', function() {
      conn1.end(); // close parent (and this) connection
    });
  });
});

暫無
暫無

聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

相關問題 使用ssh2模塊在node.js中設置sftp服務器 無法使用 Node.js ssh2 模塊將用戶切換到 root Node.js 錯誤：使用 ssh2 讀取 ECONNRESET Node.js 的 SSH2 問題 在 shell 中使用 Node 模塊 SSH2 如何通過 ssh2 Node.js 模塊（在 Electron 應用程序中）使用 SFTP 一次下載/上傳多個文件？ 節點js在ssh2中的ssh中設置超時 在node.js中沒有特定對象的require（“ ssh2”） ssh2連接錯誤后使node.js不退出 使用Node.js和SSH2從SFTP服務器讀取文件
相關標簽
 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM