- Java 双重比较
- java - 比较器与 Apache BeanComparator
- Objective-C 完成 block 导致额外的方法调用?
- database - RESTful URI 是否应该公开数据库主键?
我有一台服务器(例如,内部服务器)只能从另一台服务器(例如,外部服务器)访问,而不是运行 Node 服务器的服务器。但是, Node 服务器可以到达外部服务器。从命令行使用 ssh 时,我可以使用 ProxyCommand 配置文件语句来简化连接。我的配置文件如下所示:
Host innerserver
ProxyCommand ssh outerserver nc innerserver 22
这允许我简单地键入 ssh innerserver
,ssh 将通过 outerserver 建立隧道。现在我想使用 Node 的 ssh2 模块来实现同样的事情。在文档中它说 socks
-connect 选项可用于“连接跳跃”,但它从未说明确切的含义或您将如何使用它。我尝试了以下方法:
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
似乎从来没有真正建立起内在联系。我做错了什么?
最佳答案
更新:您最好使用 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
});
});
});
关于node.js - 使用 Node.js ssh2 模块模拟 ssh 的 ProxyCommand,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/22174280/
我用运行 Node node --debug app OR node --debug-brk app 它有反应 debugger listening on port 5858 Express serv
这个问题在这里已经有了答案: What is the difference between (int *i) and (int* i) in context of both C and C++? [
我有一个应用程序,它通过消息队列将数据库写入命令分派(dispatch)给工作人员(数量非常大),因此无法保证它们的接收顺序。 我有两个 Node ,例如“Account”和“Media”。在此假设的
有没有办法在调用 ts-node 时将选项传递给 Node ?我正在尝试在 Node 中使用一个实验性功能,如果它能与 ts-node 一起使用,那就太好了。 这就是我目前正在做的事情: ts-nod
我有一个容器化的Node应用程序,它在DigitalOcean服务器上运行。当我更新服务器上的应用程序时,该应用程序必须关闭一小段时间。为了能够更新应用程序并避免停机,我目前正在阅读零停机时间部署/蓝
我正在编写一个 Node.js 应用程序。我正在使用 request 和 Cheerio 加载一组 URL 并获取该网站的大量信息,现在假设我想要获取的只是标题: var urls = {"url_1
如果不弹出以下错误,我无法安装任何 Node.js 模块。错误代码引用package.json文件。如果知道为什么会发生这种情况,我们将不胜感激。 最佳答案 这些不是错误,它们只是警告。一切都应该如此
如果我运行(从我的项目目录中): supervisor javascripts/index.js 我得到:/usr/bin/env: Node :没有这样的文件或目录 如果我运行: node java
我已遵循使用 Node-Inspector 的所有步骤 但是当我打开应用程序时,我在控制台上看不到任何脚本或日志。 我的应用程序在端口 4000 上运行。我认为唯一可能发生冲突的是端口 8080 上的
我在android中使用rxjava2,有时会遇到这样的问题: Observable.fromArray( // maybe a list about photo url in SD
我目前正在使用 Node 光纤来编写同步服务器端代码。我主要通过 try-catch block 进行错误处理,但外部库或其他小部分异步代码中总是有可能发生错误。我正在考虑使用新的域功能来尝试将这些错
看起来node-debug是node-inspector周围的一个shell?分别什么时候应该使用? 最佳答案 如果您安装node-debug,您只能访问node-debug命令。 如果您安装node
我目前正在代理后面工作,该代理不允许我执行此命令的 HTTP GET 请求阶段: Node node-sass/scripts/build.js 请求阶段: gyp http GET https://
听说node js可以用在服务端。我以前用过jsp。 jsp页面内部的java代码对客户端是不可见的。如果 Node js 只是 javascript,那么它如何对客户端不可见? 最佳答案 首先,No
我正在为 Node native 插件从 node-waf 构建迁移到 node-gyp 构建系统。 node-gyp 说它支持多个目标版本,但我在使用 node-gyp 时找不到如何指定目标 Nod
给定一个 $node ,我正在尝试在以下两种输出该 $node 的方式之间做出决定。 要么 $output = theme('node', $node); 或 node_build_content($
如果package.json中的窗口A打开一个新窗口B,node-main如何访问它?这是我的代码: package.json { "main": "index.html",
我试图在我的 xml 中的特定节点 ( ) 之前插入一个注释节点。这是它的方法: function test(xmlResponse) { var parser = new DOMParse
我正在尝试做npm install wrtc使用 Node 版本 16.14.0 但这还没有完成。它在给npm error code 1所以我试图将 Node 版本更改为以前的 lts 14.19.0
当我在 Visual Studio 中运行 Node.js 应用程序时,我收到以下消息:DeprecationWarning: 'node --debug' 和 'node --debug-brk'
我是一名优秀的程序员,十分优秀!