• 1 Post
  • 17 Comments
Joined 10 months ago
cake
Cake day: February 20th, 2025

help-circle
  • The point is, if the certificate gets stolen, there’s no GOOD mechanism for marking it bad.

    If your password gets stolen, only two entities need to be told it’s invalid. You and the website the password is for.

    If an SSL certificate is stolen, everyone who would potentially use the website need to know, and they need to know before they try to contact the website. SSL certificate revocation is a very difficult communication problem, and it’s mostly ignored by browsers because of the major performance issues it brings having to double check SSL certs with a third party.













  • There’s no such thing as too simple to document. If you spent time learning how to install it, you’ll need to relearn it if you want to make any changes in the future. If you don’t leave at least some notes as to why you make some decisions, you’ll have to redo your work.

    It’s also good to make notes on every configuration setting. That forces you to understand why the settings are the way they are. If you have a -f in a docker config and you don’t have any understanding of why that’s there, you might not know if it’s a development flag for getting things set up, or if it’s a critical part of your environment.

    It is especially important if any of those parts are exposed to the public Internet. You might have a config set to allow unauthenticated connections and not know it.