1. ShellShock: 'bash' vulnerability

    A vulnerability in 'bash', popularly called 'ShellShock' has been all over the news this week. I've spent a lot of time talking to clients about it over the last couple of days, and checking up on systems, so I thought I'd write some of those conclusions down.

    read more
  2. Make your own Client-side Certificates with a Pseudo CA

    I've used this authentication method on a couple of different client projects so far, so I thought it might be useful to write up a quick explanation of how it works.

    Client-side Certificates

    The webserver can be configured to ask for a client-side certificate, for example in apache:

    SSLCACertificateFile ...
    read more
  3. FreeTDS without udp 1434

    Just a quick note for anyone trying to do FreeTDS through a tunnel or a firewall pinhole or whatever: If you specify an Instance name, FreeTDS goes and probes UDP 1434 to determine the port number for that instance, even if you also explicitly specify the TCP port number you ...

    read more
  4. More Trickiness With SSH

    I saw an article on reddit about SSH trickery. SSH is a very subversive protocol, able to work around many kinds of unwise security policies. Here’s a couple more useful things to know.

    1. Better Lurking Through .ssh/config-ery.

    Where you’ve got machines lurking behind other machines, inaccesible ...

    read more
  5. wget –certificate=$X –private-key=$X

    wget 1.10.2 seems to silently fail to use an SSL client certificate unless you specify both –certificate and –private-key:

    wget --certificate=$PEMFILE --private-key=$PEMFILE

    Even though both things are in the same .PEM file. It does read and check the PEM file if you specify only the former ...

    read more