In which new tarballs appear

February 12, 2010

HotSSH 0.2.7

So I took a bit of free time to fix up some things in my semi-toy project hotssh. If you like it, you should upgrade since this release fixes some major bugs with the connection tracking, and some more minor things.

The project’s at the point where though if I wanted to do anything noticeably more compelling, I’d have to either take the leap of using a real SSH library (maybe libssh?) rather than invoking OpenSSH as a subprocess. The problem is that gets into a lot of complexity in trying to stay in sync with whatever OpenSSH does (key management, known_hosts etc.). Probably someday though.

dbus 1.2.20

In the category of less user visible but probably more important, a new stable DBus is available. There are fixes larger and smaller (the real changelog is from 1.2.18 which was a paper bag release). I think one of the most important for mobile Linux users is the patch to switch to the monotonic clock; basically DBus will be more reliable if you suspend the system or reset the system clock. Besides other reliability fixes, there are some other small nice things like a better dbus-monitor. Thanks to Tom Hughes of Palm for the former, and Lennart Poettering of Red Hat and Will Thompson of Collabora for the latter!

And now back to some more user-visible GNOME Shell work; as Jon mentioned it looks like some new contributors are outpacing me, while I’ve been working on some of the underlying St toolkit infrastructure. Time to catch up!

4 Responses to “In which new tarballs appear”

  1. Andrew Says:

    If I may be so bold, Some feature requests for HotSSH.

    I use it every day, and it has some fantastic features already. The Tabbed sessions and sftp open is very useful.

    However, there’s a few thing I’d love to be able to do with it. (in no particular order)

    Save sessions with a friendly name, as I deal with dozens of servers on a daily basis, I can often come back to reconnect to a server to find it’s slipped off the bottom of the history, and even then, I’d have to remember it by IP rather than a friendly name that means something to me.

    Also, a method by which the login credentials can be saved, both username AND password. Even if this requires a ‘master password’ to open the application to maintain some degree of security.

    Also saveable configurations such as ssh tunnels, keepalives and other useful stuff.

  2. Ryan Says:

    I use it everyday as well and I agree with all of Andrew’s suggestions.

    Keep up the good work and thanks for the handy piece of software.

  3. Graham Lyon Says:

    I looked into using a real SSH library recently for a project I’m working on (the project will now be written in python, but I was researching for writing it in C…). The conclusion I came to was libssh2 as its namespace is less polluted than libssh. It has many good features, including agent support in the release that’s in the lucid repos. Hope this helps🙂

  4. Erick Says:

    I second… third what Andrew asked for – it would be much appreciated.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: