Google SWE teaches systems design | EP46: Certificate Transparency (SSL/TLS)

แชร์
ฝัง
  • เผยแพร่เมื่อ 4 ม.ค. 2025

ความคิดเห็น • 7

  • @ashshkapoor
    @ashshkapoor 2 หลายเดือนก่อน +1

    I was watching one video per day and reading about the same topic that day. Thank you so much for this Jordan! ❤

  • @rezamonang
    @rezamonang 3 หลายเดือนก่อน +1

    Thank you for this. Now i have no life to binge watch all of your videos.

  • @dibyaranjanmishra4272
    @dibyaranjanmishra4272 2 ปีที่แล้ว +4

    Really helpful once again.

  • @raj_kundalia
    @raj_kundalia ปีที่แล้ว +2

    got some good idea for the basic at least in the first half of the video! thank you.

  • @YGendy
    @YGendy 2 หลายเดือนก่อน +1

    Just dumping a question I had in mind, how will bogus certificate be revoked given that the log is append-only. ChatGPT said CAs maintain a CRL (Certificate Revocation List), was too lazy to ask it what happens if that list gets compromised tho

    • @jordanhasnolife5163
      @jordanhasnolife5163  หลายเดือนก่อน

      I'll be honest with you I don't know this off the top of my head, perhaps worth consulting google. Let me know what you find!

    • @shadyabhi
      @shadyabhi 13 วันที่ผ่านมา +1

      It is CA's job to declare this revocation. This revocation is typically advertised by either the CRL list (older) or via OSCP. To optimize and reduce latency, OSCP stapling is also something worth reading about.