Comment

Comment on Decreasing Certificate Lifetimes to 45 Days

cron@feddit.org ⁨2⁩ ⁨weeks⁩ ago

The best approach for securing our CA system is the “certificate transparency log”. All issued certificates must be stored in separate, public location. Browsers do not accept certificates that are not there.

This makes it impossible for malicious actors to silently create certificates. They would leave traces.

source

Sort:hotnew top

False@lemmy.world ⁨2⁩ ⁨weeks⁩ ago
Isn’t this just CRL in reverse? Part of the point of cryptographically signing a cert is so you don’t have to do this if you trust the issuer.

source
- cron@feddit.org ⁨2⁩ ⁨weeks⁩ ago
  No, these are completely separate issues.
  
  CRL: protect against certificates that have their private key compromised
  
  CT: protect against incompetent or malicious Certificate Authorities.
  
  This is just one example why we have certificate transparency. Revocation wouldn’t be useful if it isn’t even known which certificates need revocation.
  
  The National Informatics Centre (NIC) of India, a subordinate CA of the Indian Controller of Certifying Authorities (India CCA), issues rogue certificates for Google and Yahoo domains. NIC claims that their issuance process was compromised and that only four certificates were misissued. However, Google is aware of misissued certificates not reported by NIC, so it can only be assumed that the scope of the breach is unknown.
  
  Source
  
  source
- Auli@lemmy.ca ⁨2⁩ ⁨weeks⁩ ago
  Or the more likely a rouge certificate authority giving out certs it shouldn’t.
  
  source
Arghblarg@lemmy.ca ⁨2⁩ ⁨weeks⁩ ago
This seems like a good idea.

source
- cron@feddit.org ⁨2⁩ ⁨weeks⁩ ago
  The only disadvantage I see is that all my personal subdomains (e.g. immich.name.com and jellyfin) are forever stored in a public location. I wouldn’t call it a privacy nightmare, yet it isn’t optimal.
  
  There are two workarounds:
  
  do not use public certificates
  
  use wildcard certificates only
  
  source
  - Burnoutdv@feddit.org ⁨2⁩ ⁨weeks⁩ ago
    But how to automate wildcard certificate generation? That requires a change of the txt record and namecheap for instance got no mechanism for that to automatically happen on cert bot action
    
    source
    cron@feddit.org ⁨2⁩ ⁨weeks⁩ ago
    There are some nameserver providers that have an API.
    
    When you register a domain, you can choose which nameserver you like. There are nameservers that work with certbot, choose one that does.
    
    source
    -> View More Comments
    clif@lemmy.world ⁨2⁩ ⁨weeks⁩ ago
    Doesn’t caddy support that (name cheap txt mod) via a plug-in?
    
    I haven’t tried it yet, but the plugin made it sound possible. I’m planning to automate on next expiration… When I get to it ;)
    
    I did already compile caddy with the plugin, just haven’t generated my name cheap token and tested.
    
    source
    -> View More Comments