inThirty

Before we start, we must say, we don't condone stealing from anyone. We are not providing any show notes, nor making any recommendations. Tom and I argued about this episode before deciding it should be done. Torrenting and piracy will happen, but we should explain how to do it safely. This is one of those topics where people aren't going to listen to not do something, so showing them the best way, is probably the right thing.

While not a security topic per say, Tom and Chaim are drone curious. They decided to look into the issues associated with drones. Should you be worried that they will turn into annoying gnats on a summer's eve, or just a passing fad.

Not much here other than the Apple Watch.  We talk about how the keynote went, and weather any of us will buy one? Spoiler: Chaim won’t.

Not much here other than the Apple Watch.  We talk about how the keynote went, and weather any of us will buy one? Spoiler: Chaim won't.

Nothing major happened this week, but we do have a bunch of little stories. We give Tom four minutes each story, and let him explain to us what is going on. Moxie Marlinspike | PGP Ars Technica | Hillary ran her own webserver Journalism Tools for Privacy WSJ | SIM Card Theft Ars Technica | Hard Drive Firmware Hacking ZDNET | FREAK Whisper Systems | Signal Encryption App Ars Technica | Google not requiring encryption on lollipop

#superfish is here. Tom and I talk about what this means, and more importantly how to remove it if you are infected. We talk about how this happened, how researchers found the "feature" and what this means to Lenovo.

We take a look at the decision brought forth by the FCC, and what it means to be a utility as defined by Title 2. Chaim takes the side of maybe a law in 1934 is too old, and should be written for today’s technology. Show Notes: Netflix Tweet Battle for the Net FCC Rules

We take a look at the decision brought forth by the FCC, and what it means to be a utility as defined by Title 2. Chaim takes the side of maybe a law in 1934 is too old, and should be written for today's technology. Show Notes: Netflix Tweet Battle for the Net FCC Rules

https://youtu.be/MM6JIHWAsYg We take a look at Charlie Miller's new venture (hacking cars), and what that means. Basically, we should all be scared. The good news? Charlie and crew properly disclosed the issues, and a fix was issued before their presentation. Show Notes: Wired

Tom takes us through some more news articles in the next thirty minutes, but we mainly focus on the Anthem personal identifiable information leak. Again we talk about what to do, what to watch out for. Next we talk about FIDO and Windows 10 wanting to destroy the password.

Tom brought us a few good topics to discuss. Let us know if the audio has gotten any better. http://www.wired.com/2015/01/german-steel-mill-hack-destruction/ http://www.forbes.com/sites/thomasbrewster/2015/01/28/ransomweb-50000-dollar-extortion/ https://www.yahoo.com/tech/can-hackers-really-take-over-your-car-110827803044.html

First off we start with a special announcement. We are going to focus more on quality of audio and content, more than doing a show every week. We talk about the two news hosting stories of the week. Brian Williams being suspended, and Jon Stewart leaving the Daily Show. We discuss our TV news watching habits.

First off we start with a special announcement. We are going to focus more on quality of audio and content, more than doing a show every week. We talk about the two news hosting stories of the week. Brian Williams being suspended, and Jon Stewart leaving the Daily Show. We discuss our TV news watching… Continue reading inThirty 174 – DVR’d News

First off, unless there is a demand for weekly, I think we are going to go every other week. In this episode we get a viewer email showing us a bad Google permissions bug. We spend the show talking about the bug, what the emailer did (all correct), and what happens when nothing gets done. Tom wrote a blog post detailing it, which you should take a look at. Show Notes: The Blog of Tom Webster Gunnar Haid

What happens when your business decides to control every part of the desktop environment?