1

I have an issue with ssh2 library in Node.js.

I'm trying to run a command on some host in ssh, using this libaray. The host's response may be long, so when it cross the 4096 length of chars in the respose string, it stops the data streaming, so I don't get the whole answer, but only the 4096 first chars.

This is my sshService.js, where I calls the exec function, with the command string to run:

const Client = require('ssh2').Client;

const exec = (command) => {
   const conn = new Client();

   return new Promise((resolve, reject) => {
      conn.on('ready', () => {
         let result = [];
         conn.exec(command, (err, stram) => {
            if (err) throw err;
            stream
               .on('close', () => { conn.end(); resolve(result); })
               .on('data', async (data) => { result.push(await data.toString()); })
               .stderr.on('data', (data) => { reject(data.toString()); })
         })
      }).connect(host: HOST_IP, port: 22, username: USERNAME, password: PASSWORD);

      conn.on('error', err => { conn.end(); reject(err); return; });
   })
}
Naor
  • 337
  • 1
  • 3
  • 11
  • Two unrelated issues with the code you've posted: 1) `await data.toString()` does nothing, so using `async` is also useless; 2) Calling `data.toString()` has the potential to result in corrupt output for multi-byte characters. If you're expecting UTF-8 text output, call [`stream.setEncoding()`/`stream.stderr.setEncoding()`](https://nodejs.org/docs/latest/api/stream.html#readablesetencodingencoding) appropriately so that you'll get complete strings instead of raw bytes. – mscdex Nov 30 '22 at 05:51

0 Answers0