-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancing to "ipcrypt" #22
Comments
For the network layer, there's IPsec as well as some security extensions On Wed, Jul 9, 2014 at 11:16 AM, Sworddragon [email protected]
Aseda Gyeke Aboagye |
Hm, in this case I'm wondering what is the main difference (except the different layers) between tcpcrypt and IPsec. Does IPsec after installing/configuring also automatically encrypt if the other site supports it and fallback to plaintext if not? |
IPSec fell into the "design by committee" trap, it tries to solve all possible problems for all possible use cases, which makes it so complex and fragile that most security-conscious people recommend to avoid it entirely. There were attempts to make IPSec fully opportunistic, but it turned out to be a failure. And it would have introduced lots of state into a layer that should be stateless. In this light, tcpcrypt seems like a very reasonable compromise. |
tcpcrypt is designed to encrypt only TCP connection so I was thinking what about to go a layer down? Would it be possible to encrypt all network data that is delivered over ip connections or would this cause technical problems? If tcpcrypt would be able to really encrypt all network traffic this would be a very nice enhancement.
The text was updated successfully, but these errors were encountered: