Skip to content
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

Open
Sworddragon opened this issue Jul 9, 2014 · 3 comments
Open

Enhancing to "ipcrypt" #22

Sworddragon opened this issue Jul 9, 2014 · 3 comments

Comments

@Sworddragon
Copy link

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.

@aaboagye
Copy link

aaboagye commented Jul 9, 2014

For the network layer, there's IPsec as well as some security extensions
for IPv6.

On Wed, Jul 9, 2014 at 11:16 AM, Sworddragon [email protected]
wrote:

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.


Reply to this email directly or view it on GitHub
#22.

Aseda Gyeke Aboagye

@Sworddragon
Copy link
Author

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?

@intgr
Copy link
Contributor

intgr commented Jul 23, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants