Cameron's Pensieve

I’ve been meaning to write this post for a while, but I only found the right sort of excuse to do it today. At work I was playing with VirtualBox’s RDP (Remote Desktop Protocol: like VNC but much better) and wanted to do some work on it from home on my old Mac laptop, which is a PowerPC G4 and therefore basically useless when it comes to anything regarding virtualisation, so I needed to connect to TCP 127.0.0.1:3389 on my offic machine where VirtualBox (actually, I had started it with VBoxHeadless). But to get there, I first have to SSH into a gateway, and then from the gateway, SSH into my office machine… this calls for some gymastics.

Read more...

I have recently purchased a NetComm NP285 Turbo HomePlug Twin Pack from TradeMe, which are Ethernet over Power bridges. Information regarding standards and so forth can be found at the HomePlug Powerline Alliance. In brief, these particular adaptors work at up to 85Mbps (earlier version was 14Mbps and up and coming version at 200Mbps).

This post is trying to give you some information about the performance I was able to attain in my flat, which is quite old, both with regard to typical round-trip-time and throughput.

Read more...

Some years ago, 2004 by the looks of it, I had created a simple script (wrel) to get an idea of how reliable my wireless link was, and have since updated it with a slightly better user interface (it now has a progress guage) and it uses a sub-second interval when run as root. In particular, I wanted to get some impression of how often there was some sort of retransmission event. You can’t tell this from any link-layer, and I wanted something more general, in order to observe the spread of round-trip-times over internet links, wireless links, and even HomePlug (Ethernet over Power). Ping gives a useful metric for this.

Rdiff-Backup provides a fairly nice way of backing up a server, and I have used it to back-up a number of different servers, each with a different version of rdiff-backup. This is annoying because although a version 1.1.15 should work with 1.1.12, for example, in reality it does tend to complain.

Because of this version-skew on different types of servers, I took the approach of having multiple versions installed on the backup server (Mac OS X Panther in the first case, and now Leopard). This document details how you can house multiple versions of the rdiff-backup server on the same machine and use a different version per-client.

You can find the documentation and supporting files in the Files section.

What with all the hubbub with the OpenSSL faults in the news recently, I deciced I would do something to put down another large problem I have with a closely related product–OpenSSH, although I should immediately point out that this is not necessarily particular to OpenSSH.

You see, OpenSSH has very little support for easily creating rich access policies. The access policy I wanted to create was to allow password authentication to clients inside our campus, but only allow public-key authentication to clients coming from outside the network.

The reason for this, as anyone running an Internet-facing SSH server will be able to immediately appreciate, is that every day many login requests are made from the Internet to SSH servers, trying to brute-force account names and passwords; sometimes they are successful, but most of the time it just creates a lot of noise in the logs and an uneasy what-if feeling in your gut.

Read more...