Comment on Decreasing Certificate Lifetimes to 45 Days

• CosmicTurtle0@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ 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.

  source
• fxdave@lemmy.ml ⁨3⁩ ⁨weeks⁩ ago

  not all phones support manually adding certs

  source

  • Auli@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

    Which phones. Android and iOS could.

    source

    • fxdave@lemmy.ml ⁨3⁩ ⁨weeks⁩ ago

      I don’t know about iOS, but Android had support for this in the past. Now the support is partial. It’s no longer possible to install system-level certificates. Or at least they made it extremely inconvenient.

      source
  • False@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    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.

    source

    • fxdave@lemmy.ml ⁨3⁩ ⁨weeks⁩ 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.

      source
• Valmond@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  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…

  source

  • Unforeseen@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

    No, because it’s no longer dangerous if it’s trusted.

    You give your friends your public root and if applicable, intermediary certs. They install them and they now trust any certs issued by your CA.

    Source: I regularly build and deploy CA’s in corps

    source

    • Valmond@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      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?

      source

      • Unforeseen@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

        Openssl can do everything.

        That’s right, but instead of the word derived we use “issued”

        Correct certs get old by design, they can also be revoked. As another commenter mentioned the biggest pain is actually in the redistribution of these end certificates. In enterprise this is all managed usually with the same software they use for deployment or have auto enrollment configured.

        You should find tons of guides just take it slow to understand it all. Understanding certificates in depth is a rare and good skill to have. Most sysadmins I come across are scared to death of certificates.

        source

        • -> View More Comments
  • IsoKiero@sopuli.xyz ⁨3⁩ ⁨weeks⁩ ago

    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.

    source

    • Valmond@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Thank you! This is actually precisely what I need, you IT guys are the best!

      source
  • helios@social.ggbox.fr ⁨3⁩ ⁨weeks⁩ ago

    No that’s the point. If you import the CA certificate on your browser, any website that uses a cert that was signed by that CA will be trusted and accessible without warning.

    source