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

Consider padding to preserve traffic flow confidentiality #18

Open
sebdeckers opened this issue Aug 13, 2019 · 2 comments
Open

Consider padding to preserve traffic flow confidentiality #18

sebdeckers opened this issue Aug 13, 2019 · 2 comments
Labels
security Security enhancements or fixes

Comments

@sebdeckers
Copy link
Member

sebdeckers commented Aug 13, 2019

@sebdeckers
Copy link
Member Author

sebdeckers commented Aug 13, 2019

COSIC CRYPTOGRAPHY BLOG, COUNTERMEASURES: PADDING

We also simulate constant padding, i.e., all TLS record packets are padded to have the size of the maximum TLS record observed in the dataset. This padding strategy, as shown on the table of Figure 7, defeats the classifier by reducing its success rate to less than 7%.

@sebdeckers
Copy link
Member Author

https://github.com/nodejs/node/blob/5207dec0175de92116262e8382d6ac57def3a203/src/node_http2.cc#L802-L852

Padding strategy ideas:

  • Padding based on random amount per packet
  • Padding aligned to N-bytes. (Currently fixed at 8. Could use expensive JS callback to emulate.)
  • Apply padding only to HEADERS or DATA frames.

@qoelet qoelet changed the title Padding Consider padding to preserve traffic flow confidentiality Aug 13, 2019
@qoelet qoelet added the security Security enhancements or fixes label Aug 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security Security enhancements or fixes
Projects
None yet
Development

No branches or pull requests

2 participants