SecureShell Go 1.4.3

Connecting to a cloud box for the first time now works the way people
actually do it: copy the command the console gives you, paste it in.

Paste the command your console hands you

AWS gives you something like:

ssh -i "my-key.pem" ubuntu@ec2-3-111-164-59.ap-south-1.compute.amazonaws.com

Pasting that into quick connect used to make everything before the @
into the username, so the server rejected an account called
ssh -i "my-key.pem" ubuntu. Quick connect now reads the whole command:
quoted key paths (spaces included), -p, -l — which loses to a user@
on the operand, as OpenSSH does — bare switches like -v -A -T, flag
values that must not be mistaken for the host, a trailing remote command,
and ssh:// URLs. IPv6 keeps working throughout.

The file named by -i is remembered and shown, not opened: it is
relative to whatever directory you would have run the command in, which
this app has no way to know, and guessing could load the wrong key.

Import a key file, and keep the host

Quick connect gains the Import key file button it never had, so a
.pem no longer has to be pasted as text. The host editor's version of
that flow moved into one shared implementation rather than a second copy.

After a connection succeeds, quick connect offers to save the host
instead of leaving a button to be noticed. The offer never delays the
session, and declining is not asked twice.

Fixes

• The quick connect screen no longer freezes after a successful
  connection. The app theme gives every filled button an infinite
  minimum width so buttons fill a column; inside a row that fails layout
  for the whole subtree, leaving a title bar above a blank page with
  nothing on screen to explain it. The widget tests now build with the
  real app theme — the default one has no such rule, which is exactly why
  they passed while the screen was broken.
• If a key is in PKCS#8 format, which the SSH library cannot read, the
  message now names the command that converts it rather than only saying
  it is unsupported.