Well, if you can intercept the request to the server to can also change that parameter of the TLS certificate hash.
What is actually modified since you cloned the Seafile sourcecode? I found this in the sourcecode: <div class="other-info fright"> <!-- <p>Server Version: 3.1.7</p> <p>© 2014 Seafile</p> <p><a…
"Tomorrow, we'll publish a full post on the nitty, gritty techical details of how, what has come to be called Keyless SSL™, works."
People are trying for almost 15 years to replace IPv4. That's almost impossible, 96% of the traffic worldwide is still IPv4. This project is dead on arrival.
Isn't this what SPDY try to implement?
Well, if you can intercept the request to the server to can also change that parameter of the TLS certificate hash.
What is actually modified since you cloned the Seafile sourcecode? I found this in the sourcecode: <div class="other-info fright"> <!-- <p>Server Version: 3.1.7</p> <p>© 2014 Seafile</p> <p><a…
"Tomorrow, we'll publish a full post on the nitty, gritty techical details of how, what has come to be called Keyless SSL™, works."
People are trying for almost 15 years to replace IPv4. That's almost impossible, 96% of the traffic worldwide is still IPv4. This project is dead on arrival.
Isn't this what SPDY try to implement?