“Your commanders admit they are training the people they have sent you to die fighting”, said one of the messages posted on the site.![]()
Tag Archives: Vulnerability
Skype can no longer be crashed with these eight characters
Bad week for messaging apps, with Skype choking on http://: and iOS on… well, it hasn’t been fixed, so let’s just say “some characters!”![]()
SSCC 200 – If you can’t trust the IRS, whom can you trust? [PODCAST]
Join Sophos experts Chester Wisniewski and Paul Ducklin as they dissect the latest security news in our weekly podcast. It’s entertaining and educational – news you can use!![]()
You STILL support encryption designed to be crackable in 1995? 60 Sec Security [VIDEO]
Watch this week’s “60 Second Security” – the one-minute news roundup video with attitude!![]()
Anatomy of a LOGJAM – another TLS vulnerability, and what to do about it
We’ve had BEAST, Lucky Thirteen, BREACH, BEAST, POODLE, Heartbleed and FREAK…now, it’s LOGJAM. Paul Ducklin explains, and tells you what you can do about it.![]()
SSCC 199 – Don’t panic, it’s not really as VENOMous as you thought [PODCAST]
Our latest weekly security podcast – the VENOM bug, iris recognition, a spyware company breach, and ID trouble at the Passport Agency. Happy listening!![]()
The phone that keeps an eye on your eyes – 60 Sec Security [VIDEO]
The latest episode of our weekly “security news in one minute” video. Enjoy…![]()
SSCC 198 – “Fusking”? Did I hear that correctly? [PODCAST]
A week of many patches, Lenovo in the news again, an anti-forensic tool with a misleading name, and the rudely-named “sport” of Fusking. Listen to our latest straight-talking security podcast…![]()
The VENOM “virtual machine escape” bug – what you need to know
Here’s what you need to know about VENOM, the latest security vulnerability to be given a marketing-friendly name. If you’re using any virtual machines, read this to set your mind at rest…![]()
Lenovo uses System Update to patch serious System Update security hole
Responsible disclosure and an exploitable hole closed neatly through the exploitable process itself. Result! (But make sure you’ve patched.)![]()
