2 Talks: Cryptography 101 & Cracking passwords & Why L33t!fied passwords are bad


Details
UPDATE: THIS IS NOW A SECURITY DOUBLE HEADER!
Join us ONLINE -----> https://www.ssw.com.au/live
TALK #1 : Cryptography 101 with Robert Boedigheimer
Learn the fundamentals of cryptography, including public/private and symmetric encryption, hashing, and digital signatures. Discover which techniques are appropriate for various situations. Review practical real life examples for storing passwords, protecting URL parameters, securely exchanging information with partners, and safely encrypting sensitive information on public web sites. Concepts apply to all platforms, examples will be in C# for both .NET and .NET Core.
About the Speaker:
Robert Boedigheimer is the Principal Systems Developer at Schwan's Home Delivery providing business solutions with web technologies in the US.
He is a Microsoft MVP, a Progress Developer Expert (Fiddler), an ASPInsider, a Pluralsight author, and a 3rd degree black belt in Tae Kwon Do. Robert regularly speaks at national and international events.
Profile: https://sessionize.com/robert-boedigheimer/
TALK #2: Cracking passwords and why L33t!fied passwords are bad with Alexei Doudkine
Join us in a live demo of how a hacker who has broken into your machine can quickly and easily get your password hashes, take them offline and crack them to retrieve your original password. In this interactive talk, we'll discuss how passwords are stored in Windows, some techniques real-world hackers will use to crack password hashes and what you can do to prevent yours from being cracked.
About the speaker:
Hacker, tinkerer, car modder and "the dog guy", Alexei has been in the offensive security space for over 10 years. From hacking into networks and applications, to gaining physical access into buildings, Alexei specialises in breaking into thing. He runs a company called Volkis and wants to keep the old school hacker culture alive (think Hackers, the movie).

Sponsors
2 Talks: Cryptography 101 & Cracking passwords & Why L33t!fied passwords are bad