3 ms·
> In my opinion if you’re lazy enough to warrant a wildcard cert then you’re too lazy to do security properly anyway, period. You don't present yourself in a w
by lclarkmichalek 9y ago
> In my opinion if you’re lazy enough to warrant a wildcard cert then you’re too lazy to do security properly anyway, period.
You don't present yourself in a way conductive to convincing anyone of anything.
- dijit 9y agoRegardless of the format; the statement still stands, even if it's overly combative. There is functionally no requirement for wildcard SSL that can't be met another way- the other ways in almost all cases are better for user security. Not designing for it (just like not designing for cloud failure) isn't someone being belligerent about nothing it really only emerges out of laziness or unwillingness. (or, you have a legacy application which is architected a certain way, which is similar in my scenario of having a "non-cloud ready" application.. it's not a good reason to architect things in future this way)
- dijit 9y agoI wrote a less combative follow up: https://blog.dijit.sh/follow-up-wildcard-tls-certificates https://blog.dijit.sh/follow-up-wildcard-tls-certificates