No, with these reasons:
- Bandwidth isn’t plenty
- My “uptime” at home isn’t great
- No redundant hardware, even a simple mainboard defect would take a while to replace
I have a VPS for these tasks, and I host a few sites for friends amd family.
No, with these reasons:
I have a VPS for these tasks, and I host a few sites for friends amd family.
It’s quite obvious from the context
It is good that they are easier to read, because they are about as long as the first book of The lord of the rings.
I think the cost of all the additional wiring and components would outweight the benefits.
What if the sun isn’t shining? You would need a heat pump that can use AC and DC. What if the sun is shining, and the water is hot enough? Your PV would need DC cabling and a converter to AC to send power to the grid. And all these components would need some switches etc.
It’s just easier to have all your home run on AC.
You’re right, Google released their vision in 2023, here is what it says regarding lifespan:
a reduction of TLS server authentication subscriber certificate maximum validity from 398 days to 90 days. Reducing certificate lifetime encourages automation and the adoption of practices that will drive the ecosystem away from baroque, time-consuming, and error-prone issuance processes. These changes will allow for faster adoption of emerging security capabilities and best practices, and promote the agility required to transition the ecosystem to quantum-resistant algorithms quickly. Decreasing certificate lifetime will also reduce ecosystem reliance on “broken” revocation checking solutions that cannot fail-closed and, in turn, offer incomplete protection. Additionally, shorter-lived certificates will decrease the impact of unexpected Certificate Transparency Log disqualifications.
Sorry, I understood you wrong. You’re right!
Nothing of value was lost when EV certificates disappeared.
even more secure with the 90 days policy.
Yes, if you do this manually it will work.
I meant certbot with nginx plugin and http-01 challenge.
You’re right, ssl.com offers this, too.
IMO, sticking to manual processes that are error-prone is a waste of money and not a sign of a honest business.
Yes, it can be easier. But not every DNS provider allows API access, so you might need to change the provider.
(good luck with that in many enterprise scenarios).
I’ve set it up fully automated with traefik and dns challenges.
Letsencrypt issues wildcard certificates. This is however more complicated to setup.
AFAIK, the only reason not to use Letsencrypt are when you are not able to automate the process to change the certificate.
As the paid certificates are valid for 12 month, you have to change them less often than a letsencrypt certificate.
At work, we pay something like 30-50€ for a certificate for a year. As changing certificates costs, it is more economical to buy a certificate.
But generally, it is best to use letsencrypt when you can automate the process (e.g. with nginx).
As for the question of trust: The process of issuing certificates is done in a way that the certificate authority never has access to your private key. You don’t trust the CA with anything (except your payment data maybe).
At least for me, this works out of the box.
Some requirements:
I agree, but I understood this question in the context of a homelab.
And for me, a homelab is not the right place for a public website, for the reasons I mentioned.