DEF CON 26 CRYPTO AND PRIVACY VILLAGE - Scott Arciszewski - No Way JOSE! Designing Cryptography
DEFCONConference2 HN recommenders · recommended in 2 months, 2019-2020
7K views · 7 years ago · talk · evergreen
Scott Arciszewski's DEF CON 26 Crypto and Privacy Village talk critiquing the JOSE standards (JWT, JWS, JWE) and showing how to design cryptographic tokens more safely.
HN recommends it as the video version of the argument that JOSE/JWT is a flawed standard, and as a help in understanding token design choices.
24:20Satoshi Has No Clothes: Failures in On-Chain Privacy by Ian Miers (Devcon4)
Ethereum Foundation
5K views • 7 years ago
46:22DEF CON 19 - Moxie Marlinspike - SSL And The Future Of Authenticity
DEFCONConference
11K views • 13 years ago
1:06:36Computer Security 161 Cryptocurrency Lecture
Nicholas C Weaver
128K views • 4 years ago
28:11Ben Kreuter RWC 2017
Real World Crypto
1K views • 9 years ago
40:21Bitcoin - Unmasking Satoshi Nakamoto
Barely Sociable
1.6M views • 6 years ago
48:02BlackHat USA 2011: SSL And The Future Of Authenticity
Christiaan008
95K views • 15 years ago
45:37Beyond Passwords: Secure Authentication with Mozilla Persona
Next Day Video
3K views • 13 years ago
1:02:52Joanna Rutkowska: Towards (reasonably) trustworthy x86 laptops
media.ccc.de
27K views • 10 years ago
25:14Rick Reacts to Lightning (Again) and brings up a previously undiscussed flaw
We Are All Satoshi
14K views • 8 years ago
21:28DEF CON 26 - Christopher Domas - The Ring 0 Facade Awakening the Processors Inner Demons
DEFCONConference
24K views • 8 years ago
53:40GrapheneOS: Documenting Numerous Attacks Against CalyxOS,, Techlore, & More
Techlore
135K views • 5 years ago
22:36Computer Scientist Explains One Concept in 5 Levels of Difficulty | WIRED
WIRED
7.2M views • 4 years ago
48:29DEF CON 30 - Sam Bent - Tor - Darknet Opsec By a Veteran Darknet Vendor
DEFCONConference
557K views • 4 years ago
12:24Elliptic Curve Back Door - Computerphile
Computerphile
554K views • 8 years ago
59:2328c3: The Science of Insecurity
28c3
42K views • 14 years ago
52:51DEF CON 22 - Zoz - Don't Fuck It Up!
DEFCONConference
546K views • 11 years ago
12:42I Think I Know Who Satoshi Is
TheTedNelson
246K views • 13 years ago
3:37Why Web Filters Don't Work: Penistone and the Scunthorpe Problem
Tom Scott
3.6M views • 10 years ago
42:50DEF CON 18 - Moxie Marlinspike - Changing Threats To Privacy: From TIA to Google
DEFCONConference
7K views • 13 years ago
4:30Matthew Driver “Trust Is A Critical Component” | Perspectives | Channel NewsAsia
CNA Insider
27K views • 11 years ago
3 comments from Hacker News
I've been doing a similar thing recently. I found PASETO to be interesting ( link ), which is a lot like JWT but is simpler and more opinionated (e.g. there is no plaintext option; symmetric and asymmetric operations are cleanly separated; etc.). I especially enjoyed watching this video ▶ this video I still decided to go with JWT, since PASETO isn't yet standard and its software hasn't been around for long, but it definitely helped me understand more about the choice I was making. In particular, PASETO distinguishes between "local" tokens (producer and consumer can both use the same symmetric key) versus "public" tokens (producer and consumer can't use the same key, e.g. third party services run by different organisations; hence asymmetric keys are needed). PASETO encourages local tokens to be used when possible, since their keys can be shorter, they generate shorter tokens, they're faster to encrypt/decrypt, they're easier to rotate, etc.; public tokens are essentially a last resort when we must interact with a third party. I was originally considering 'public' JWTs (i.e. asymmetric keys) for my use case, since we're using AWS API Gateway and that has the option to check the signatures of 'public' JWTs, and reject invalid ones before they ever hit my code. However, I eventually went with 'local' JWTs (i.e. symmetric keys), since the convenience of having AWS discard some tokens for us wasn't worth the (mostly logistical) overhead of using asymmetric keys. My choice to use the J
If you like video consumption, a DEFCON 2018 talk by the author Scott Arciszewski on this same topic can be found here: No Way JOSE! Designing Cryptography: ▶ this video You're welcome :) Edit: Clarify that Scott is the author of both post and video.
Blog post: link DEFCON CPV talk: link + ▶ this video Alternative design that isn't radioactive: link Apologies if this wasn't more readily available or commonly known. I'm worse at marketing than I am at engineering.