Conversation

Notices

1. :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Monday, 24-Jun-2019 15:35:18 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy:
   @absturztaube this post sponsored by NSA
   1. :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Monday, 24-Jun-2019 15:38:19 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy:

      in reply to
      @absturztaube
      
      wow this guy has no fucking idea how PKI works, does he? compromising the CA at most provides an extremely marginal path to a session KEK (by issuing a new cert), since the CA does not possess any privkeys. and all CAs have this problem, not just Let's Encrypt.