B
B
boodda2012-11-16 23:33:42
Computer networks
boodda, 2012-11-16 23:33:42

In light of the prohibitions, why not use encryption at the level of HTTP headers?

Problem: HTTP browsing.

One of the solutions:

the client sends an HTTP packet in which the HOST and URL are encrypted with a public key algorithm, which is registered in the TXT record of the domain. The server decrypts the HOST and URL, transfers it to the site, the site gives the content, SSL is not required to maintain the connection

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
Stdit, 2012-11-16
@Stdit

Because the filters, it seems, have not yet reached the level of the HTTP protocol. Sites are blocked by IP and by domain. Domain blocking can be easily bypassed by setting a non-blocking DNS, or even better by setting DNSCrypt. And IP blocking is through VPN.

V
vsespb, 2012-11-16
@vsespb

This is an invention and implementation of a new protocol. If you can do this, then it’s easier to implement SSL on all sites without exception. The result will be the same.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question