printf(" SaltwaterC ");

I had this article in my pipeline for ages, but in a time of shifting priorities and, well, life, it took a bit to finally sit down and put words on paper.

Not to jump on any bandwagons, but this situation is getting now to ridiculous levels.

The tragedy of passwordless sudo I believe the definition of security theatre says it all: “the practice of taking security measures that are intended to provide the feeling of improved security while doing little or nothing to achieve it”.

So, what’s the fuss about having access to Docker socket?

Do know know the old saying in the security circles that all input is evil?

TL;DR plug the ethernet cable coming from the modem into a port configured as WAN (i.e has a masquerade rule to the interface in the SNAT section).

There are various guides about how to get Chef on a Raspberry Pi, but none I could find about how to build a proper Chef client package.

This one took some effort.

Getting G.fast in my area was kind of a bad news – no plans for FTTP any time soon.

I’ve this router for the sole reason that it is a recommended piece of equipment for doing WiFu, but as as I previously mentioned, it fails to do its job.

Let’s assume the following use case: you’ve gathered enough frames containing a valid WPA handshake, but you missed the mgt frame containing the ESSID.

Fortunately, the wireless card from Apple’s hardware supports the monitor mode.

In my previous rant I was telling how notoriously difficult is to get the right hardware.

Well, getting a Netgear WNR1000v2, one of the recommended access points by WiFu, was also a pain in the ass since the product is EOL.

Update: I made something which I call aircrack-db.

I found out that using persistent connections greatly improves the productivity when working with SSH.

Due to the HeartBleed SNAFU, I needed a quick solution for getting the information from a certificate deployed on a remote machine.

At some point, I wrote this piece about how much computing file hashes in node.js used to suck.

Marius once told me about portspoof.

For some reason I need that.

There’s a lot of wrong information floating on the internets.

Background libxml-to-js was born to solve a specific problem: to support my early efforts with aws2js.

I heard a lot of urban legends about the Windows Update service that messes up your machine.

I needed some reusable stuff that splits a string every nth char.

There’s no news that pretty often the popular code hosting services, like GitHub or Bitbucket, go down when you least expect it.