Signal-Chief is Now “Secure”

You likely haven’t noticed yet, but if you look at the top corner of your browser, you should be seeing a little lock symbol up there for the first time (at least when you came to this site). For years now, Signal-Chief has been served up on straight HTTP. I was never really worried about it because there is no personal information on the site, and the only person who actually logged into it was me (and I use unique passwords on everything)

Screwing Around with IPTables When It Doesn’t Play Nice

Firewall

So you may not have noticed (hopefully) but I recently moved signal-chief from a shared hosting instance on GoDaddy to a dedicated VPS system. As a cyber guy, one of the first things I wanted to do was to start with some basic security so of course step one is to run yum update to update all of my packages, and step two was to setup some firewall rules. To allow me to initial a connection (DNS, http, whatever) from the server and get the return traffic back. Unfortunately when I tried to run this command I got “iptables: No chain/target/match by that name” sent back to me. Well that’s frustrating.

Translating Geek to Geek

Nerdy Grunt

Imagine this scenario…. “The first neutron passes the LD and engages enemy position.  The enemy position is destroyed and the damage is extensive enough to cause an adjoining position to catch fire.  When the ammunition in that adjoining position explodes it takes out another position…” Huh?