Release v0.9.1

This is just a bugfix release over v0.9.0: there were some fatal bugs in our docker communication which have been fixed.

Release v0.9.0

Hello friends, it's a new fwd release! We have some pretty good new features this time around:

• Better colors and symbols for broken ports Now, if something goes wrong opening a port on the client side, the UI will be marked with a red ✗. Disabling and re-enabling the port will retry, in case it was something transient. (Thanks @quodlibetor!)

• Docker port descriptions If docker is running on the remote system, fwd will now attempt to enumerate all of the listening ports of running docker containers. This might not work if the user you've connected as doesn't have permission to talk to the docker daemon, or if your docker daemon is not listening at the default location.The remote side must be updated for this to work. (This feature was contributed by @quodlibetor, but re-implemented by @DeCarabas, so if it doesn't work it's my fault. Thanks @quodlibetor!)

• Better logging The new --log-filter option controls the logging level on the remote side, which make it easier to debug certain failures. Both the local and remote side must be updated for this to work. (Thanks @quodlibetor!)

• Anonymous ports In the past, fwd has restricted itself to sending port descriptions only when it could positively identify the process that was listening on the port. This was for security reasons: if it couldn't get the command line and file descriptors of the process then we assumed that it was a system process and wasn't safe to forward. However, this can be a little restrictive sometimes, and so the new policy is to report all of the listening ports, but not enable them by default. This way, if there's something that fwd cannot identify, it can still be forwarded manually without resorting to complicated hacks. Both the local and the remote side must be updated for this to work.

• Experimental clipboard support You can now send up to 256MB of text from the remote side to the local side with the fwd clip command. fwd clip <some file> will send the contents of <some file>, and fwd clip - will read from stdin and send that. This can be useful for sending over logs or output or anything just a little too big to copy/paste from the terminal, without having to reach for scp. (This is still early, so please do report any problems with it.)

Thanks and happy fwding!

Release v0.8.1

This just bumps the version on the crate, a step I forgot to do last time.

Release v0.8.0

Just a small release this time, with better error messages:

• Now the URL is displayed whenever fwd-browse fails to connect.
• Now the exact reason for the connection failure is displayed.

The latter message is not very... pretty, but it might provide some clue as to what's going wrong.

Release v0.7.0

A small fix and a small feature:

• Pass the --sudo flag to run the server side with sudo, allowing the server side to discover all ports on the computer. This will include ports like port 22 from sshd, and port 53 from systemd! Use this with caution.
• Don't crash if someone tries to move the selection when there are no ports at all.

Release v0.6.2

This release has a number of UI improvements!

• Vertical motion with j and k now match the corresponding vi motions
• ? brings up a help window
• The selection wraps around the top and bottom of the list, so that moving up at the top of the list selects the last element, and down at the bottom selects the first

Enjoy!

Release v0.5.0

A small release; new command line handling, and a --version argument.

Release v0.4.0

This is the first proper release of fwd. The main thing to note is that now there is a fwd-browse binary, which attempts to open the browser on the host machine if somebody is connected with fwd. Very handy for e.g. SSO from a remote machine.