Zig
Zig
Read Data from an SSH Channel
See more SSH Examples
Demonstrates the Chilkat Ssh.ChannelRead method, which reads incoming SSH channel messages. The only argument is the channel number; the ReadTimeoutMs property limits how long it waits. Received data is appended to the channel's receive buffer, then retrieved with a GetReceived... method.
The integer return value is -1 on error, -2 if nothing arrived before the timeout, 0 if EOF or channel close was processed, or — when greater than 0 — the total bytes currently buffered for the channel (not the bytes newly received by this call).
Background: SSH reading is a two-step pattern that trips people up at first: the
Channel* read/poll methods move bytes from the network into an internal per-channel buffer, and a separate GetReceived... call hands that buffer to your code. A positive return is therefore a buffer total, not a count of what this call fetched. Note that a 0 return means EOF or close — buffered data can still remain and should be drained.Chilkat Zig Downloads
const std = @import("std");
const chilkat = @import("chilkat");
pub fn main(init: std.process.Init) !void {
const alloc = init.arena.allocator();
// Demonstrates the Ssh.ChannelRead method, which reads incoming SSH channel messages. The only
// argument is the channel number. The ReadTimeoutMs property limits how long it waits.
const ssh = try chilkat.Ssh.init();
defer ssh.deinit();
const ssh_port = 22;
ssh.connect("ssh.example.com", ssh_port) catch {
std.debug.print("{s}\n", .{try ssh.getLastErrorText(alloc)});
return;
};
// Normally you would not hard-code the password in source. You should instead obtain it
// from an interactive prompt, environment variable, or a secrets vault.
const password = "mySshPassword";
ssh.authenticatePw("mySshLogin", password) catch {
std.debug.print("{s}\n", .{try ssh.getLastErrorText(alloc)});
return;
};
const channel_num = ssh.openSessionChannel();
if (channel_num < 0) {
std.debug.print("{s}\n", .{try ssh.getLastErrorText(alloc)});
return;
}
// Start a shell WITHOUT requesting a PTY. Without a PTY the shell sees it is connected to a
// raw data pipe and enters non-interactive mode: it suppresses the command prompt, does not
// echo typed commands back, and skips interactive login scripts. The output is therefore
// clean and easily parseable -- but because no prompt is ever sent, code must not wait for
// one. Instead, have each command print a predictable marker, or wait for EOF / channel close.
ssh.sendReqShell(channel_num) catch {
std.debug.print("{s}\n", .{try ssh.getLastErrorText(alloc)});
return;
};
ssh.channelSendString(channel_num, "uname -a\n", "utf-8") catch {
std.debug.print("{s}\n", .{try ssh.getLastErrorText(alloc)});
return;
};
// The return value is: -1 on error, -2 if nothing arrived before the timeout, 0 if EOF or
// channel close was processed, or the total number of buffered bytes when greater than 0.
const result = ssh.channelRead(channel_num);
if (result == -1) {
std.debug.print("{s}\n", .{try ssh.getLastErrorText(alloc)});
return;
}
if (result == -2) {
std.debug.print("No channel data arrived before the timeout.\n", .{});
}
if (result == 0) {
std.debug.print("EOF or channel close was processed. Buffered data may still remain.\n", .{});
}
if (result > 0) {
std.debug.print("Total bytes buffered: {d}\n", .{result});
}
const output = ssh.getReceivedText(alloc, channel_num, "utf-8") catch {
std.debug.print("{s}\n", .{try ssh.getLastErrorText(alloc)});
return;
};
std.debug.print("{s}\n", .{output});
ssh.disconnect();
}