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)
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.
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?
As anyone who has spent more than an hour or two driving around the box at NTC knows, it can be pretty damn easy to get lost in the desert, especially at night under blackout conditions. After 3.5 years there, I got pretty good at knowing my way around the box but during each rotation there was always at least one or two times where I would get turned around and have no idea where the hell I was
Today Signal-Chief.com is joining the likes of Github, Google, Amazon and host of countless others who are protesting the FCC’s proposal to end its current policy of Net Neutrality.
I was looking through Nixcraft on Facebook yesterday (if you haven’t been to it before, check it out) and came across the graph. As a warrant officer, we’re supposed to be experts in whatever field it is that we happen to be in. But what exactly does that mean?
One thing that I first noticed occasionally as a Net Tech, and then more as an OC/T at NTC and finally a ton now that I have moved into the cyber side of the world is the just how important logs can be. The problem….we suck at actually saving the stupid things.
Hello from the right coast. According to the date on my last post, it has been 304 days since I last posted although I thought it had actually been considerably longer. So what has been happening in the last 43 weeks and 3 days?
By and large I personally think that most of us are much more comfortable with layer three than any other layer in the OSI model. We deal with it each and every day. We have a number of tools at our disposal which make it very easy for us to see if/when it’s working and just how the data is traveling. To start with though, we have to know just how things are supposed to work.
When I entered the Army in July 1999, I came in as 31F (switch operator). Anyone who worked with MSE will remember that it had almost absolutely no data capabilities, but also that it was extremely easy to troubleshoot. Signal flow for MSE was pretty darn easy to understand. If you understood the idea of how the system worked, the signal flow was easy to follow. With the introduction of JNN and IP data networks to tactical communications, logical and physical said “It’s been fun” and headed their separate ways leaving our operators and even ourselves busy scratching our heads wondering how the hell it all worked.