3 ms·
The same can be said about using SSL/HTTPS to access websites. People say it's secure because no one can intercept, but at the same time it verifies you are the
by rootsudo 5y ago
The same can be said about using SSL/HTTPS to access websites. People say it's secure because no one can intercept, but at the same time it verifies you are the one who did that at that time.
Also, heartbleed.
- 3np 5y agoHow? I see with DKIM there is a clear tie to the owner embedded in the signature, but what identifying info can you get from an HTTPS request?
- Ms-J 5y agoI've heard this before as well and have even seen some darknet sites not using HTTPS due to trust issues.
- denton-scratch 5y agoI guess the OP must have been thinking of client certificates, which are as rare as rocking-horse shit.
- maccolgan 5y agoYou can cryptographically prove that the server signed this payload with a valid certificate, I'm not sure if there's tools to do that but that's a possibility...
- pigeons 5y agohttps://tlsnotary.org/ https://tlsnotary.org/