†: Some things I got wrong with JS Safe 2.0 - Google CTF 2018

Channel:
Subscribers:
920,000
Published on ● Video Link: https://www.youtube.com/watch?v=J2XS3m2Ctuc



Duration: 5:30
21,002 views
980


I got some stuff very wrong, so I really felt like making a proper update video to explain it.

main video: https://www.youtube.com/watch?v=8yWUaqEcXr4

-=[ 🔴 Stuff I use ]=-

→ Microphone:* https://geni.us/ntg3b
→ Graphics tablet:* https://geni.us/wacom-intuos
→ Camera#1 for streaming:* https://geni.us/sony-camera
→ Lens for streaming:* https://geni.us/sony-lense
→ Connect Camera#1 to PC:* https://geni.us/cam-link
→ Keyboard:* https://geni.us/mech-keyboard
→ Old Microphone:* https://geni.us/mic-at2020usb

US Store Front:* https://www.amazon.com/shop/liveoverflow

-=[ ❤️ Support ]=-

→ per Video: https://www.patreon.com/join/liveoverflow
→ per Month: https://www.youtube.com/channel/UClcE-kVhqyiHCcjYwcpfj9w/join

-=[ 🐕 Social ]=-

→ Twitter: https://twitter.com/LiveOverflow/
→ Website: https://liveoverflow.com/
→ Subreddit: https://www.reddit.com/r/LiveOverflow/
→ Facebook: https://www.facebook.com/LiveOverflow/

-=[ 📄 P.S. ]=-

All links with "*" are affiliate links.
LiveOverflow / Security Flag GmbH is part of the Amazon Affiliate Partner Programm.

#CTF







Tags:
Live Overflow
liveoverflow
hacking tutorial
how to hack
exploit tutorial
john hammond
google ctf
googlectf
ctf
capture the flag
capture-the-flag
ctf writeup
ctf video writeup
write-up
tutorial
crackme
anti-debugging
anti debugging
anti debug
keygen
js safe 2.0
crack me
obfuscation
obfuscated
javascript
js
java script
chrome
developer tools
reverse engineering
algorithm