Les vidéos et slides de la DEFCON 2104
Last August, at Defcon, the hacker conference in Las Vegas, a boyish 40-year-old engineer and security researcher named Michael Ossmann stood on the stage of a lecture hall, about to detail a stunning new set of tools designed for spying on a wealth of electronic devices.
These are the videos from the Defcon Wireless Village 2014 (Defcon 22). Thanks to the Village People for putting on the event, especially Maeltac for recording.
Bitsquatting refers to the registration of a domain names one bit different than a popular domain. The name comes from typosquatting: the act of registering domain names one key press different than a popular domain. Bitsquatting frequently resolved domain names makes it possible to exploit computer hardware errors via DNS. For more details on bitsquatting my research, please see my Blackhat 2011 whitepaper. Someone has posted a youtube video of my DEFCON 19 talk about this topic. The slides from my DEFCON 19 talk are also available. Whitepaper: http://media.blackhat.com/bh-us-11/Dinaburg/BH_US_11_Dinaburg_Bitsquatting_WP.pdf Videos : http://www.youtube.com/watch?v=lZ8s1JwtNas Slides : http://dinaburg.org/data/DC19_Dinaburg_Presentation.pdf
It's finally here! DEF CON: The Documentary is now available to all! The torrent can be found at https://www.defcon.org/html/torrent/DEF CON 20 documentary 720p.torrent! We had a great premiere last night, and if you are here at DEF CON and missed it, we are showing it again tonight in Track 2 at 20:00! Keep those torrent clients running if you grab it to spread the love!
(Lien direct vers le torrent)
A lot of press has been released this week surrounding the cracking of MS-CHAPv2 authentication protocol at Defcon. For example, see these articles from Ars Technica and CloudCracker. All of these articles contain ambiguous and vague references to this hack affecting Wi-Fi networks running WPA2 security. Some articles even call for an end to the use of WPA2 authentication protocols such as PEAP that leverage MS-CHAPv2.
But they fail to paint a true and accurate picture of the situation and the impact to Wi-Fi networks. I think this is misleading, and that any recommendations to stop using PEAP are flat-out wrong!
So let's clarify things.