468
Decreasing Certificate Lifetimes to 45 Days (letsencrypt.org)
submitted 9 months ago by to c/selfhosted@lemmy.world
196 comments fedilink hide all child comments
 

Let’s Encrypt will be reducing the validity period of the certificates we issue. We currently issue certificates valid for 90 days, which will be cut in half to 45 days by 2028.
This change is being made along with the rest of the industry, as required by the CA/Browser Forum Baseline Requirements, which set the technical requirements that we must follow. All publicly-trusted Certificate Authorities like Let’s Encrypt will be making similar changes. Reducing how long certificates are valid for helps improve the security of the internet, by limiting the scope of compromise, and making certificate revocation technologies more efficient.

you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 9 months ago* (last edited 9 months ago) (19 children)

And you still can't self certify.

It's cute the big players are so concerned with my little security of my little home server.

Or is there a bigger plan behind all this? Like pay more often, lock in to government controlled certs (already done I guess because they control DNS and you must have a "real" website name to get a free cert)?

I feel it's 50% security 50% bullshit.

Edit: thank you all I will dive down the CA certification rabbit hole now! Have worked in C++ & X509 on the client side so maybe I'll be able to figure it out.

  • permalink
  • fedilink
  • source
  • hideshow 19 child comments
    •
  • [–] 24 points 9 months ago (14 children)

    You can absolutely run your own CA and even get your friends to trust it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 14 child comments
    •
  • [–] 15 points 9 months ago

    Yes you can but the practicality of doing so is very limiting. Hell I ran my own CA for my own internal use and even I found it annoying.

    The entire CA ecosystem is terrible and only exists to ensure connections are encrypted at this point. There's no validation or any sort of authority to say one site is better than another.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 9 months ago (4 children)

    not all phones support manually adding certs

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 9 months ago (1 child)

    That's a complaint about those phones not PKI in general then. Though it's surprising their enterprise support won't let you since that is (or was) a fairly common thing for businesses to do.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 9 months ago

    That's a fair point. However, on the practical side, it's sad that I would have to root my gf's phone to let her access the services we host.

    I ended up using a DynDNS and Caddy for managing my cert.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 9 months ago (7 children)

    But you have to manually accept this dangerous cert in the browser right?

    Very interesting actually, do you have any experience about it or other pointers? I might just set one up myself for my tenfingers sharing protocol...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [+] 15 points 9 months ago* (last edited 8 months ago) (3 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 9 months ago (2 children)

    Thank you!

    Is there some simple soft that let you make those certs, like with a root cert and then "derived" certs? On linux :-) ?

    I guess people have to re-trust every now and then because certs get old, or do they trust the (public partof the) root cert and the daughter certs derived from root are churned out regularly for the sites?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] 3 points 9 months ago* (last edited 8 months ago) (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 9 months ago

    I was forced to learn some of it at work (using and signing medical payment transactions, with x509 certificates) so I have ar least a starting point. I have no idea how the revoke process works though, I can't figure out a way that it functions without a central authority getting queried regularly. I thonk I can start without that knowledge though.

    Anyway, with your information I'm up and running, thank you again!

    "Derived certificates" not child certs, noted !

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 9 months ago (1 child)

    It's pretty simple to set up. Generate CA, keep key and other private stuff stored securely, distribute public part of CA to whoever you want and sign all the things you wish with your very own CA. There's loads of howtos and tools around to accomplish that. The tricky part is that manual work is needed to add that CA to every device you want to trust your certificates.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 9 months ago (1 child)

    Technically something like DANE can allow you to present DNSSEC-backed self-signed certs and even allow multi-domain matching that removes the need for SNI and Encrypted Client Hello... but until the browsers say it is supported, it's not

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] -1 points 9 months ago* (1 child)

    And you still can't can self certify.

    Skill issue, you've always been able to self certify. You just have to know where to drop the self signed cert or the parent/root cert you use to sign stuff.

    If you're running windows, it's trivial to make a self signed cert trusted. There's an entire certificate store you can access that makes it easy enough you can double click it and install it and be on your way. Haven't had a reason to figure it out on Linux, but I expect it won't be super difficult.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •