burnd0wn retweeted
Since @PortSwigger won't be producing a third edition of The Web Application Hacker's Handbook, the @Burp_Suite team is working on something better: online, interactive, actively maintained, and best of all completely free!
More details to follow soon.
burnd0wn retweeted
Dear @AppleSupport, we noticed a *HUGE* security issue at MacOS High Sierra. Anyone can login as "root" with empty password after clicking on login button several times. Are you aware of it @Apple?
burnd0wn retweeted
IoT is a boon, and a MESS. From SAINTCON 2016, Erich Ficker @eficker surveys three vulnerable IoT ecosystems: youtube.com/watch?v=mbeIdsou…
burnd0wn retweeted
Uh, folks, you may want to upgrade to iOS 10.1. Like, right now. support.apple.com/en-us/HT20…
burnd0wn retweeted
To everyone freaking out about IoT attacks: if tons of easy to hack devices was going to wreck the internet, it'd have happened years ago.
burnd0wn retweeted
DNC creates Cybersecurity board made up of well meaning people with no cybersecurity expertise. Your move Russia...
thehill.com/business-a-lobby…
burnd0wn retweeted
Keep that #DEFCON feeling all year - join a local #defcongroup! Can't find one? Start one! Defcongroups.org
burnd0wn retweeted
Replying to @mungowitz @jadler1969
cut trade ties, leave international institutions...where have I heard this before? Oh, right: – at Washington, DC
burnd0wn retweeted
Our completed @sensepost USaBUSe boards ready to be stuck in their enclosure. @defcon here we come. cc @RoganDawes
burnd0wn retweeted
@FruityWifi running on NetHunter @kalilinux . No extra devices needed, just your phone! ;)
burnd0wn retweeted
You've probably already seen the Donald Drumpf video, but in case you hadn't:
youtu.be/DnpO_RTSNmQ
burnd0wn retweeted
Is encryption tech a problem for law enforcement? @anjiecast looks at the data: mercatus.org/publication/goi…
burnd0wn retweeted
Dutch govt says no to backdoors, slides $540k into OpenSSL without breaking eye contact reg.cx/2jkp
burnd0wn retweeted
There's a real gem in this week's news involving owning Kaspersky AV using ../../ in a CNAME field of an SSL cert... (thanks to @taviso)


























