![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
This is good for bitcoin.
This is good for bitcoin.
deleted by creator
In this thread, people publically linking their age to their account.
deleted by creator
Can’t wait to hear tankie rhetoric about how all of “the west” should just surrender to Russia to save lives.
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
What was at the URL? Seemed a bit sketchty and I didn’t have the time to look it up.
deleted by creator
I think it’s important to distinguish use case. Or make more qualified statements instead of saying self signed certs are always more secure.
Like, are we talking about a single certificate pair per service contained on your local isolated network? Sure probably then.
Otherwise, very likely not.
Please feel free to explain your stance more, also I’m not an expert. But that seems like a potentially dangerous statement. Certificates are a multifacted issue which cannot be covered by “Self signed certs are more secure”. Even in an environment you are fully managing intermediate and leaflet certificates, you want the root issued by a public CA. Ideally an EV CA. If the infrastructure is fully internal, there are still advantages to using an external CA (like for getting a root cert) unless you are able to securely generate, store, revoke, cycle, and manage the root certificates. As for trusting certificate chains, again multifaceted, but they fix a lot more problems than they cause and increase security posture. Having one off pairs per service at any but the smallest scale is security nightmare fuel.
Lol obligatory /s Irony is lost on Lemmy.