4 ms·
What is so difficult about encrypting HTTP with an SSL Layer? SSL is a key you keep and an unlocked padlock you give someone. They use it to give back a box w
by digitalsushi 13y ago
What is so difficult about encrypting HTTP with an SSL Layer?
SSL is a key you keep and an unlocked padlock you give someone. They use it to give back a box with no idea how to open it.
You configure a web server with a key and a padlock. It keeps the key and serves the padlock. How can this be improved? (Serious question, maybe it can - this concept still seems esoteric to many)
- X4 13y agoSSL has the concept of many central authority organs (many of them got compromised or hand their private keys to government agencies), there is the proposal of a web-of-trust to counter that, but it's not there yet. Hmm, do you suggest a new protcol/idea/improvement? A TCP/IP alternative also needs a security layer (not necessarily SSL though). No offense, but if it's so easy, then you may know something many scientists and researchers and cryptographers haven't discovered, in any case I'm happy and all ears, if you are willing to contribute to a solution.. http://en.wikipedia.org/wiki/Secure_Socket_Layer http://en.wikipedia.org/wiki/Secure_Socket_Layer
- gsnedders 13y agoReplacing SSL/TLS just because of the current CA system is absurd. Nothing in either requires CAs (indeed, in theory anyone can issue a root certificate, and that's very much a feature). The issue is how to convey what certificates are legimite and which are not, and that's a tangential issue to whether you allow trusted subtrees or not.