Edit History
Optional description
What to report
Reason
Report

DtSR Episode 344 - You've Probably Been Pwned 2019 Podcast Ep.

DtSR Episode 344 - You've Probably Been Pwned DtSR Episode 344 - You've Probably Been Pwned
00
Affinity
0%
0.5
0%
1
0%
1.5
0%
2
0%
2.5
0%
3
0%
3.5
0%
4
0%
4.5
0%
5
0%
Recent Ratings
First Ratings
Top Tags
Top Lists
Not added to a list yet. :(
My Tags
No tags added.
My Lists
Not added to a list.
Choose a list
New list name
New list description
Item description
My Catalog
Length
40m
Country
United States
Release Dates
2019-05-01
Description
This week, Rafal is joined by the man, the myth, the Aussie legend - Troy Hunt. We basically talk about whatever is on his mind - which, as it turns out is a lot. Take a listen, we may publish an English translation later (joking, Troy!).   Highlights from this week's show include... Troy gives a run-down on HaveIBeenPwned We talk through some of the interesting use-cases for HaveIBeenPwned data Troy gives perspective on usernames, passwords, and other important things technology/security related Guest Troy Hunt ( @TroyHunt ) - Troy is a Microsoft Regional Director and Most Valuable Professionalawardee for Developer Security, blogger at troyhunt.com, international speaker on web security and the author of many top-rating security courses for web developers on Pluralsight. I created HIBP as a free resource for anyone to quickly assess if they may have been put at risk due to an online account of theirs having been compromised or "pwned" in a data breach. I wanted to keep it dead simple to use and entirely free so that it could be of maximum benefit to the community. Short of the odd donation, all costs for building, running and keeping the service currently come directly out of my own pocket. Fortunately, today's modern cloud services like Microsoft Azure make it possible to do this without breaking the bank!
Podcast
provider
host
No host added (Edit page)
Other Roles
No other roles added (Edit page)

Reviews

All Reviews
No reviews yet. :(

Comments

No comments yet. :(
Reason for report
Description