Re:Letsencrypt, the Good, the Bad and the Ugly
by aeturnum on Thursday September 10, 2020 @01:39PM
(#24434658)
I don't think this is "contempt for users," it's a position that configurations that appear to setup a web server to run without monitoring for years are deceptive and harmful to the admin taken in by them. It's an ethical (and technical) position that tools should push their users to adopt maintenance practices that are seen as responsible by the wider community. It's not contempt to inform people about the level of work you expect is required to do what they are planning. It's also, if letsencrypt happens to be wrong, not contemptuous to be wrong!
Re:Letsencrypt, the Good, the Bad and the Ugly
by lallysingh on Thursday September 10, 2020 @05:28PM
(#24436744)
The one with contempt for users is reality itself. Computer security is hard, and whatever you have installed today will force you to update it later, directly or indirectly, due to security.
Don't blame the messenger.
Re:Letsencrypt, the Good, the Bad and the Ugly
by boudin on Thursday September 10, 2020 @07:19AM
(#24431172)
I don't think that's what the author says.
There's been some changes in the past to the acme protocol requiring to update whatever client you use.
Re:Letsencrypt, the Good, the Bad and the Ugly
by msla on Thursday September 10, 2020 @01:19PM
(#24434409)
It isn't contempt to realize that security landscapes change, and what was best practice in the past is insecure now.
Re:Letsencrypt, the Good, the Bad and the Ugly
by RandoHolmes on Thursday September 10, 2020 @07:57PM
(#24437866)
That's not a Python specific problem, but otherwise I agree with your point.
This kind of contempt for users is why I try to avoid using any libraries/software written in Python. Somebody always thinks their minor backwards incompatible change is such a precious snowflake that it justifies wasting collectively thousands of hours of users' time debugging and updating their stuff to work around it.