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

Why would payloads already be encrypted? #3

Open
natevw opened this issue Jun 3, 2015 · 0 comments
Open

Why would payloads already be encrypted? #3

natevw opened this issue Jun 3, 2015 · 0 comments

Comments

@natevw
Copy link

natevw commented Jun 3, 2015

All payloads are encrypted before transmission regardless of if they are already encrypted.

My understanding is that this is facilitate consistent packet handling, so the requirement makes sense but not sure why its highlighted here. Under what circumstances might you expect an example of doubly-encrypted transmission to happen? Doesn't seem like you'd try forward HTTPS or something over a TMesh link to begin with due to its throughput.

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

1 participant