The Slightly Disgruntled Scientist 7% more viral!

Rubbish Review Debut: The Noontec N5 NAS

| Comments

I recently became the proud owner of a Noontec N5 network attached storage (NAS) enclosure. I bought it because I needed:

  1. Network access to the contents of a large hard drive.
  2. USB access to the contents of a large hard drive.

It’s hard to tell where to start with this amazing device, so let’s go with the all-important first impression. Nothing says factory quality control quite like a few dead cockroaches stuck to a random sticky pad inside the enclosure. From that point on, I knew I was in for a treat.

The cockroaches could not be removed. It’d probably void the warranty anyway.

Network setup

It assembled fine, so I powered it up and connected it to my network. It then insisted on hijacking my router’s IP address, acting as a DNS server, and generally screwing up my entire network. Seems reasonable. In order to access it I had to remove it from my network, connect a Linux box directly via ethernet, use ifconfig/route/etc to manually set up network access to it, and then configure it to not be monumentally stupid.

Easy as.

Then it was time to set up SMB. Seemed to go easy enough: my Mac machine could connect, my Windows 8 machine could connect, my Linux machine… not so much. I progressed through using smbclient, mount.cifs, and eventually even Wireshark to figure out what the problem was. You might think, “well, Linux has never been great at SMB, of course you need to do some work there.” But hold your judgement until you hear the problem: to authenticate SMB connections, the N5 uses NTLMv1. NTLMv1 has a number of terrific vulnerabilities that could be exploited by a 13 year old with a graphics calculator, so NTLMv2 was created in 1996 to address some of these issue. The N5 does not support NTLMv2. That is, the N5’s level of network security predates Internet Explorer v3.

No matter. I’ll just explicitly downgrade my security settings. Cool.

Side note: the N5’s web interface exposes all passwords in plain text. Super useful feature that.

During this process, by the way, I contacted Noontec for help. They have a website, of course — the support email address listed there is for another company and offer firmware downloads off Dropbox. Seems legit. When I contacted them via this address, they suggested I start by updating the firmware, and sent me a link to do so. The firmware completely changed the branding of the box (as reported by the web UI and network protocol responses). I initially worried about the potential for malware, but realised that even running a botnet off a NAS could only improve the functionality of the N5.

So now I can check off item one on my list, and all it took was manual network routing and byte-for-byte packet inspection. On to item two: USB access!

Qanda’s Razor

| Comments

Imagine this situation: you and someone else, perhaps a friend or relative, are on different sides of a political issue. You both go to watch a debate, or panel discussion, or some similar public forum. You hear both sides argue their cases and it gradually occurs to you that it’s really one sided. The organisers have picked speakers for your side whose expertise isn’t really relevant, or who don’t really know what they’re talking about, or can’t really articulate a case.

You come out of the event, ready to say this, but your companion tells you first: “that was really one sided. They really set up my side to fail.”

How could both of you feel this way? Is it necessarily the case that one of you is right about the debate having an agenda, and one of you is wrong?

Well, maybe, sometimes. But I think we often leap to this conclusion far more often than it actually applies. I think what’s also likely is something I call the Qanda Illusion.

The illusion

The Qanda illusion applies to a situation where a debate, forum, discussion etc. features such poor presentation of both sides of the argument that people on either side will see bias against them.

This happens because there’s a fair chance you don’t know the opposing case as well as your own. You’ll notice every time your own advocates screw up, but you won’t notice the other side’s omissions. You will assume that the other side is fully utilising the chance to present its best arguments. You’ll hear the same arguments you’ve rebutted in your own head a thousand times, and wonder why no one on your side is addressing them.

But anyone on the other side of this will see exactly the same problem applied to their case!

The illusion is that although the debate appears to be skewed, there is no bias. There is only the pretence of evidence or other information and a failure to deliver all around.

A Letter to Vice-Chancellor Johnson

| Comments

Last week I sent a letter to Prof. Paul Johnson, Vice-Chancellor of the University of Western Australia (the school what I went to). The letter concerned his recent decision to circumvent the usual decision making processes and just throw university resources at a “consensus centre” set up for professional climate-change-water-muddier Dr Bjorn Lomborg at the bequest of our current government.

The Letter

Dear Professor Johnson,

I am deeply concerned with your recent decision to accept funding to house a policy centre specifically for Dr. Bjorn Lomborg at the University of Western Australia.

You are no doubt aware that to be an academic researcher of any sort in Australia is to be in a tenuous and thankless position. It is widely acknowledged that the scarcity of dedicated research funding, unreliability of funding allocation, and the overall lack of planning around research policy in Australia all mean that many promising early and mid-career researchers are simply denied the opportunity to pursue valuable and highly-regarded research. I count myself among them.

In this environment I would have hoped to see the upper levels of UWA governance add to calls to improve Australia’s research policy and the processes by which new and existing research is initiated and sustained.

Instead, you have arbitrarily dedicated UWA’s resources to court a single celebrity in a way that circumvents all mechanisms for academic integrity and merit. For the same amount of money involved, the government could instead fund four or five Future Fellowships.

A Hybrid Kali/Debian Wheezy Live Distro

| Comments

There are two things that I particularly love doing: security auditing, and tinkering with live distributions. It is very intriguing to see exactly how weak or strong your own electronic devices are against various attacks, and sometimes very contrary to expectations.

This is, of course, an extension of my usual love of seeing exactly what new and strange things I can get my old electronic devices to do, which brings us to live distributions. Live distros are simply operating systems designed to work from removable media, usually across multiple, different devices. For example, I once turned an old laptop into an ethernet/wireless bridge for my games console, by creating a live distro that ran off a USB stick. Boot with the USB stick: it’s a bridge! Without the USB: it’s my old laptop again! This gets even better if you’re dealing with embedded systems, systems with no permanent storage, etc.

(Live distros are also a gateway drug to stateless distributions, which are absolutely fascinating for repeatable engineering processes, testing, compliance, etc.)

Kali is Amazing

Given these two interests, it’s amazing that I hadn’t heard about Kali Linux until last week. Kali is a Debian-based OS, primarily designed for live usage, that is all about security testing.

So what?

Anyone who has ever tried security testing from their main OS knows what a pain it can be. Patch these drivers. Downgrade these packages. Install this thing from git. Oh no it sprayed random files all over your meticulously managed distro lol oops sorry not sorry…

But Kali gives you a nice, safe live distro, complete with patched drivers, recent kernels, up-to-date software, etc. Run it, mess around, hack on whatever, check to see if the router you bought from that dodgy shop in Ultimo patched a nasty WPS vulnerability, then reboot back into your normal day-to-day OS.

I felt like a ninja. In a tuxedo. WITH POISON DARTS.

There Was But One Problem…

…and that was, Kali didn’t work too well on my machine. When using the virtual consoles (accessed by ctrl+alt+f1), I would have missed or repeated keystrokes. I couldn’t do serial debugging when running under Qemu. There were extra utilities that I wanted to install, and some cruft that I wanted to remove. Then I discovered that Kali actually provides instructions and repositories for building your own Debian-based live image.

At this point I’m just drunk on sheer technological possibility.

I’ve used live-build a lot before, and it’s a wonderful tool. Its major drawback is that it’s a fast-moving target, and Kali seems to be a little behind. Using the instructions on the website proved problematic with the version of live-build (4 point something) in Debian Wheezy (which is what I use for packaging and certain kinds of tinkering).

When I tried simply using live-build with the Kali repos as the main package source (as per their git repo), the live-config hooks didn’t run, which meant the live user wasn’t set up, the serial console wasn’t available, and so on.