18th July 2015SSH daemon port
I am totally sold to the explanations on why putting SSH on any other port than 22 is a bad idea but it is my experience that keeping enabled the port 22 is asking for problems. It can be restricted to explicit IP addresses, etc, but, otherwise, changing the port seems a sound idea. Mind you, it is probably just discarding the unexperienced vector attacks, but even so, unless you are the unique user in that machine and keep a good password policy, a vector attack can eventually score, so disabling the port 22 and moving anywhere else can indeed help.
In Debian Jessie (8.x), it is just needed to link the ssh daemon itself and ensure that the configuration files for the duplicated daemon are in place; the following procedure does not remove the access to port 22, it is your responsibility to disable it or to enhance its security (like limiting inbound IPs, etc). See the whole procedure here
12th July 2015Ubuntu workspaces
I like enabling workspaces in Ubuntu, and then my favourite shortcuts are Super+number workspace to switch to the given workspace.
It is possible to open the preferences, go to keyboard and then update the navigation shortcuts so that 'Switch to workspace 1' is done with 'Super+1', and so on. But this won't work, because the launcher uses directly Super - so Super + 1 launches instead the first application in the launcher, Super + 2 the second one and so on.
However, these shortcuts are not editable in the preferences. Instead, it is needed to install CompizConfig Settings Manager, launch it and select Ubuntu Unity Plugin. Under Launcher, the default key to show the dash Launcher and Help Overlay is Super. Change this to something else, like Alt+Super, and the shortcuts for Workspace navigation will work as expected!
12th July 2015Reading point
Only one audiobook in the last months -that I finished, in fact I started a few others that I considered not good enough-, devoting much more time to paperbacks. And the focus was on fiction, with a lot of AI: snowcrash, and even better, Revelation Space. The counter weight was Winter of the World, still fiction, but with a lot of historic background.
1st June 2015libguestfs-tools
Using KVM on Debian, I have prepared some scripts to perform usual tasks with images, and some of those scripts rely on the package libguestfs-tools to do the heavy tasks, such as resizing partitions in the images. The scripts run perfectly in Debian Wheezy, but in Debian Jessie, I was surprised with the error message:virt-resize: error: libguestfs error: copy_device_to_device: /dev/sdb2: write: No space left on device
Which seems to be an existing bug, already solved. I could compile myself the sources, or try the package distributed in Debian Sid, with version 1.28.10 instead of 1.28.1, but I had no idea on how to install a specific package from Sid. The best answer was in this thread:
mv /etc/apt/sources.list /etc/apt/sources.d.list/jessie.list echo "deb http://debian.mirror.root.lu/debian/ sid main" \ > /etc/apt/sources.d.list/sid.list echo APT::Default-Release \"jessie\"\; \ > /etc/apt/apt.conf.d/99defaultrelease
With these changes, I differentiate the usual sources, which get precedence against the unstable ones, that contain only Debian Sid
apt-get update apt-upgrade apt-get -t sid install libguestfs-tools
This strategy is general to use a second set of sources. It can cause side effects, obviously, so it should be used in limited cases, specially when installing packages with many dependencies. In my case, it installed version 1.28.10 which solved my problem with virt-resize.
5th May 2015Moving to Bitbucket
With the incoming demise of Google Code, I had to move my TableFilter Java library out. The easy move was to migrate the code to Github, as Google provided a script to do the move at once, but that would mean leaving Mercurial and embracing Git. Mind you, that would be all but a dramatic decision: it must be impossible to work with source code without using Git -in fact, the opposite is probably not the case for Mercurial-. But all things considered, I wondered why not giving Bitbucket a shot and stay with the minor number of changes.
The move to Bitbucket was totally painless. As soon as the hosting was different, this meant updating the pom files for the project, updating some documentation, etc. So now the library has a new home. Farewell, Google code.
18th March 2015TableFilter v5.1.2
With the closure of Google code, where this project is hosted, I need to evaluate whether moving it to Github or Bitbucket. I favor Mercurial, so most likely Bitbucket will be the destination.