Why Heartbleed is a Good Thing
Yeah, Heartbleed was pretty bad. But know what would be worse? Going on, assuming everything was okay. Exposed technical vulnerabilities gets us to question our assumptions and make sweeping improvements, improving all of our security.
Don't get me wrong: Heartbleed wasn't a shining moment in tech security and I'm not super-glad that the vulnerability occurred. Still, personally, I'm pretty happy when stuff like this hits the fan.
Well, I suppose I'm glad in a "question authority" kind-of-way. When a wide-ranging vulnerability like this is brought into the open, it gets us in the technology security field off of our butts to, one, provide a remedy to the most immediate problem, but two, question all of our assumptions.
Incidents like Heartbleed, Edward Snowden's NSA revelations, and the good work conducted by Wikileaks, gets technology professionals to look more carefully at our solutions. It forces us to think differently. These incidents also reveal certain threats that we may haven't foreseen. They also lead us down a path of hardening our all our technologies in short-order to curtail compromise. In all, situations like Heartbleed elevates all of our security postures. They make all of us safer.
Arguably, what wasn't safe was continuing to live in ignorance as Heartbleed was exploited, or, while the NSA was wiretapping private data centers without warrants, or, believing that corporations and governments always have our best interests in mind. Assuming everything is okay wasn't safe. Proving flaws and vulnerabilities - even if the outcomes are undesirable - is how we all get better.
Question authority. Further, question our assumptions. Learn, build awareness, and do better next time. That's what will improve cyber security.
R
Heartbleed Vulnerability Advisory
Russell Mickler, technology consultant, warns about the heartbleed bug.
This week, a doozy of a security risk was revealed concerning the way data is encrypted between computers and web servers on the Internet.
It's called Heartbleed and you may have heard of it by now.
If you are a client of mine - and as it is my obligation as your technical administrator - I wanted to take a minute to address my services and your exposure to this vulnerability.
Microsoft Windows Terminal Services
If you receive terminal service/remote desktop solutions from me, your services are ran on Microsoft Windows 2008 R2 servers. Inasmuch, Microsoft has confirmed that their platforms are not affected by the Heartbleed vulnerability so your site and its data and your communications between them are not subject to this risk.
Google Apps
If I manage your Google Apps environment, as of Thursday April 10, 2014, Google confirmed that they've patched all of their servers for their major services, so your mail, contacts, calendars, and so on - stuff I manage for you under Google Apps - are also secure:
http://www.engadget.com/2014/04/09/google-heartbleed-patch-info/
Online Backup
If you receive an online backup product from me, I've received a verbal confirmation from the vendor that their solutions are not subject to this vulnerability.
VOIP Phone Solutions
If you receive your VOIP solutions from me, I've received verbal confirmation from the vendor that their solutions are not subject to this vulnerability.
Third Party Website Hosts and Operators
You need only be concerned about this vulnerability if your website conducts any form of secure transaction, such as logins, taking payments, or processing orders.
If your website just serves-up webpages with information, you are not affected by Heartbleed. If your website takes in any information securely, it is likely subject to this vulnerability.
If your website or email service or backup service is hosted by a third party, it is their responsibility to patch their servers and advise you of their status. I recommend you contact them immediately for a status.
Third Party Cloud-Based Services
Nearly all websites are affected by the Heartbleed vulnerability including popular brands like Netflix, Dropbox, Twitter, Facebook, large banking institutions, and the like. The situation right now is rather fluid and broad but I'd recommend the following approach:
1. Take an inventory of the 3rd party websites that are related to your business and that you frequent; ie, your financial institution, online business software, file sharing software, and so on.
2. Visit their websites or blogs for the latest update/information about their vulnerability to Heartbleed.
3. Following their confirmation that their vulnerability has been addressed, you would want to change your password with that service at the earliest opportunity.
Android Phones
Finally, Google has confirmed that some versions of the Android (Droid) operating system are exposed to this vulnerability. The models and versions vary. Those who run Android/Droid operating systems on their phones will want to apply updates throughout the weekend or discuss this matter with their cell phone carrier/provider. To test whether or not your Android phone is vulnerable, you may wish to try this solution.
If you have any questions or concerns, please feel free to contact me.
R
HP Officejet 8600 Falls Off Network
Odd problem with HP OfficeJet 8600 falling off the network. The problem turned out to be the 5ghz radio signal interfering with the 2.4ghz signal, and causing the problem. Here's the solution.
The other day I was helping a client with an HP Officejet 8600. The printer was connecting fine to the wireless network with either a dynamic or static IP assignment. I could ping it, browse to it, and even change settings through the web console. A-okay.
Then, after just two or three minutes, it completely disconnected from the network. I couldn't ping it or browse to it. The system state LED still read that it was connected and nothing had changed in the unit's config.
Crazy-making.
It took me some time to narrow down the possibilities. What it turned out to be is the 5ghz wireless signal coming from the wireless router. The 8600 uses a 2.4ghz wireless frequency. When I disabled the radio on the router for the 5ghz network, and exclusively offered the 2.4ghz network, and cycled the power on the router, the machine stayed on the network.
Of course, this action would prevent the higher-speed network from working. Bummer-drag. But it did get the unit online and satisfy the client. I guess that's what matters.
R