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
Comment on Decreasing Certificate Lifetimes to 45 Days
Valmond@lemmy.world 7 hours ago
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.
stratself@lemdro.id 6 hours ago
Passerby6497@lemmy.world 2 hours ago
And you still
can’tcan 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.
farcaller@fstab.sh 6 hours ago
You can absolutely run your own CA and even get your friends to trust it.
CosmicTurtle0@lemmy.dbzer0.com 3 hours 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.
fxdave@lemmy.ml 6 hours ago
not all phones support manually adding certs
Auli@lemmy.ca 4 hours ago
Which phones. Android and iOS could.
fxdave@lemmy.ml 1 hour 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.
False@lemmy.world 4 hours 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.
fxdave@lemmy.ml 58 minutes 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.
Valmond@lemmy.world 6 hours 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…
Unforeseen@sh.itjust.works 5 hours 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
IsoKiero@sopuli.xyz 4 hours 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.
helios@social.ggbox.fr 5 hours 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.