Risky Business #243 -- Quickly! To Ecuador!
In this week's news segment we cover Julian Assange's attempt at martyrdom in style, claims of a Twitter outage, the cracking of 923-bit pairing-based encryption in Japan, the blackmailing of an American firm by hackers, Face.com's tragic fail, The Washington Post's stunning (not) revelation that Flame was the work of the US and Israel, AutoCAD worms, bug bounties and more!
Insomnia Security's Mark Piper tackles all that at the top of the show. He's filling in for Adam Boileau.
Also in this week's show we're chatting with Adobe's director of product security and privacy Brad Arkin. We're talking to him all about an opinion piece Bruce Schneier wrote for Forbes about twisted incentives in the vulnerability market. It's interesting stuff.
That's this week's sponsor interview.
There's no feature interview this week and possibly no podcast next week. Family stuff.
Recent Posts
-
Public satellite imagery yields a wealth of intelligence...2 days 10 hours ago
-
Awesome feature track this week. Check it out here!2 days 10 hours ago
-
Special guests The Grugq, Singe, Charl and Andrew...1 week 3 days ago
-
Pwnage! Malware! Cats and dogs living together!1 week 3 days ago
-
All your herp derps are belong to RPTs...3 weeks 3 days ago
Recent comments
- Love the Das Efx tribute.
10 weeks 3 days ago - LOL so no comment by Adobe's
11 weeks 5 days ago - Welcome back, great stuff as
14 weeks 2 days ago - AEDs are very accurate and
20 weeks 5 days ago - I did see that after we
21 weeks 15 hours ago - Great podcast, a small
21 weeks 5 days ago - Peck of pickled peppers? We
24 weeks 4 days ago - Link to Sophail: Applied
27 weeks 2 days ago - Fixed. I got autocorrected...
29 weeks 3 days ago - it's jduck, not duck
29 weeks 3 days ago


Comments
Hi Patrick, A feature/sponsored interview regarding "source code security analyzers" and their capabilities would be great. Would these tools have found last weeks MySql problem (of only validating the LSB from memcmp) or could they help spot subtle problems introduced by coders intentionally in order to make money from vulnerabilities? NIST has a long list free and commercial tools, but I'm at a loss what these tools can do (I prefer C/C++). What kind of value and at what cost do the commercial tools provide?
what about the situations where you can very covertly insert a bug that is reasonably straight-forward to exploit?
As an example, extremely subtly messing with crypto RNG's to reduce entropy, debian style.
Things that don't mess with memory corruption (which typically have defences that are expensive to exploit around)
Easy to implement, hard to detect the vulnerability introduction, easy to exploit, worth good cash, No?
Post new comment