Haystack II

According to this story in Fast Company, it seems Iranian authorities were well aware of Haystack and exploited its numerous flaws to monitor the (alleged) dissidents who had swallowed Heap’s snake oil.

I told you so.

The author of the piece, Niel Ungerleider, asks: “Can someone make a Haystack that works?” My answer remains unchanged: an unconditional, resounding “no”. Haystack is profoundly, fundamentally, conceptually flawed, because of a little thing called traffic analysis. In the words of Jacob Appelbaum, quoted in the Fast Company piece: Haystack “effectively alerts authorities that you are trying to use it.”

Skilled programming

From the VxWorks Kernel Programmer’s Guide:

Prior to VxWorks 6.0, the operating system provided a single memory space with no segregation of the operating system from user applications. All tasks ran in supervisor mode. Although this model afforded performance and flexibility when developing applications, only skilled programming could ensure that kernel facilities and applications coexisted in the same memory space without interfering with one another.

…whereas now, I guess, any idiot and his dog can write a well-behaved VxWorks application…

Haystack

This is actually old news; Haystack was shut down permanently about two weeks ago, shortly after I read about it. However, this has been nagging me ever since, so I’ll write it down anyway, just to get it out of my head.

The thing that struck me the most about the articles I read about Haystack is that, although some people have questioned the strength of its crypto, no-one pointed out what seems obvious to me:

Haystack cannot possibly work, for reasons which have little to do with cryptography. Continue reading “Haystack”