Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    DEF CON 26 CRYPTO AND PRIVACY VILLAGE - Scott Arciszewski - No Way JOSE! Designing Cryptography

    DEFCONConference

    2 HN recommenders · recommended in 3 months, 2019–2020

    YouTube

    29:12 · 7.1K views · Nov 24, 2018

    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.

    Systems, Networks & SecurityCryptographySecurity & hacking
    1. 46:22
      DEF CON 19 - Moxie Marlinspike - SSL And The Future Of AuthenticityDEFCONConference11K views • 13 years ago
    2. 24:20
      Satoshi Has No Clothes: Failures in On-Chain Privacy by Ian Miers (Devcon4)Ethereum Foundation5K views • 7 years ago
    3. 48:02
      BlackHat USA 2011: SSL And The Future Of AuthenticityChristiaan00895K views • 15 years ago
    4. 1:06:36
      Computer Security 161 Cryptocurrency LectureNicholas C Weaver128K views • 4 years ago
    5. 40:21
      Bitcoin - Unmasking Satoshi NakamotoBarely Sociable1.6M views • 6 years ago
    6. 59:23
      28c3: The Science of Insecurity28c342K views • 14 years ago
    7. 2:18:23
      Line Goes Up – The Problem With NFTsFolding Ideas19M views • 4 years ago
    8. 1:02:52
      Joanna Rutkowska: Towards (reasonably) trustworthy x86 laptopsmedia.ccc.de27K views • 10 years ago
    9. 12:01
      Why Electronic Voting Is Still A Bad IdeaTom Scott5.1M views • 6 years ago
    10. 21:28
      DEF CON 26 - Christopher Domas - The Ring 0 Facade Awakening the Processors Inner DemonsDEFCONConference24K views • 8 years ago
    11. 22:36
      Computer Scientist Explains One Concept in 5 Levels of Difficulty | WIREDWIRED7.2M views • 4 years ago
    12. 48:29
      DEF CON 30 - Sam Bent - Tor - Darknet Opsec By a Veteran Darknet VendorDEFCONConference557K views • 4 years ago
    13. 45:37
      Beyond Passwords: Secure Authentication with Mozilla PersonaNext Day Video2.9K views • 13 years ago
    14. 52:51
      DEF CON 22 - Zoz - Don't Fuck It Up!DEFCONConference546K views • 11 years ago
    15. 25:14
      Rick Reacts to Lightning (Again) and brings up a previously undiscussed flawWe Are All Satoshi14K views • 8 years ago
    16. 41:06
      "Unison: a new distributed programming language" by Paul ChiusanoStrange Loop Conference45K views • 7 years ago
    17. 42:50
      DEF CON 18 - Moxie Marlinspike - Changing Threats To Privacy: From TIA to GoogleDEFCONConference7.3K views • 12 years ago
    18. 1:10:01
      35C3 - The year in post-quantum cryptomedia.ccc.de8.4K views • 7 years ago
    19. 2:16
      Andreas Antonopoulos - 51% Bitcoin AttackRodolfo Díaz72K views • 11 years ago
    20. 28:11
      Ben Kreuter RWC 2017Real World Crypto1.1K views • 9 years ago

    3 comments from Hacker News

    1. @chriswarboJun 2020· in “Hardcoded secrets, unverified tokens, and other common JWT mistakes”

      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

      RecommendsView on HN
    2. @wadkarFeb 2020· in “Javascript Object Signing and Encryption is a Bad Standard (2017)”

      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.

      RecommendsView on HN
    3. @CiPHPerCoderJan 2019· in “How to Use JSON Web Tokens”

      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.

      CitesView on HN