I'm writing a Go program that will connect to a host via SSH using the native x/crypto/ssh library and drop an interative shell.
I'm using RequestPty(), but the (bash) shell on the remote end does not behave as expected with control codes.
When I enter various control characters, they're echoed back by my terminal:
$ ^[[A
The characters still work in the sense that if I press enter after pressing the up arrow, the previous command is run - but the control character output clobbers what should be displayed there. The same goes for tab.
Is there some straightforward way to get this to work? When I've implemented similar systems in the past it hasn't been an issue because I've just shelled out to openssh, and the semantics of process groups sort it all out.
I've studied "The TTY Demystified" and as great as it is it's not clear where to begin.
A couple of things I've thought to investigate:
- enable raw mode in my terminal - but I don't want to do this without understanding why, and it doesn't seem to do the right thing
- fiddle with the terminal mode flags
openssh itself must be doing this work correctly, but it's a real best of a code base to study.
It's not actually clear to me whether this printing is being done by my local terminal emulator or shell or by the code on the remote host.
Where do I begin?
Here is a sample of my code:
conf := ssh.ClientConfig{
User: myuser,
Auth: []ssh.AuthMethod{ssh.Password(my_password)}
}
conn, err := ssh.Dial("tcp", myhost, conf)
if err != nil {
return err
}
defer conn.Close()
session, err := conn.NewSession()
if err != nil {
return err
}
defer session.Close()
session.Stdout = os.Stdout
session.Stderr = os.Stderr
session.Stdin = os.Stdin
modes := ssh.TerminalModes{
ssh.ECHO: 0
ssh.TTY_OP_ISPEED: 14400,
ssh.TTY_OP_OSPEED: 14400
}
if err := session.RequestPty("xterm", 80, 40, modes); err != nil {
return err
}
if err = session.Shell(); err != nil {
return err
}
return session.Wait()
I've tried this with term values other than xterm: screen-256color and vt100.
For the record - in the real code, instead of just a call to session.Wait(), I have a for/select loop that catches various signals to the process and sends them on to the Session.
