mirror of
https://github.com/certbot/certbot.git
synced 2026-07-26 07:39:52 +02:00
ohemorangeandGitHub
d8acf7cea0
Part of #10183 > Option 4. Stop updating old files with security improvements. If people want to be on old software they can but then they're not getting the nice new things. We can either warn or not warn if we see people using them, either on certbot install (what, who's installing new certbot on these machines), new cert, cert renewal, or certbot update. The second two would require code changes, I'm pretty sure. I don't think we should warn too often because that's how we get people to silence all output. This is a little weird because we don't usually keep around deprecated things. We could also warn loudly and see if people complain. Or do some sort of brownout. This PR warns every time certbot is run. We could make it run less often (only when a new config file is installed, probably), but that's a more extensive code change, and honestly I think it's probably fine? But I can change it.
Apache plugin for Certbot