Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Adding SNI config #40
Adding SNI config #40
Changes from 13 commits
3062fd0
0cebc16
4a5c36e
547471b
878cb7b
bf437da
36cf77f
df00536
c5f6958
4b8fdd6
9ba01d0
b26777e
0e20465
1385d8c
5ecdafa
58b3171
3da002e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we actually want this to be deterministic - and deterministic across clients too. The ideal scenario IMO is if any two clients in region R both send requests to IP X, they both use the same SNI. So perhaps we hash the masquerade IP and use the result modulo the set of SNIs to choose an SNI. Does that make sense?
A couple of minor points with my scheme: (1) If two clients have different lists, they will not end up with the same SNI. That is okay though; I think clients should only end up with different lists if they're in different regions. In that case, we don't need them to use the same SNI. (2) If the SNI list changes, then SNI-to-IP mappings will change. This is okay too; I don't expect us to change the SNI often.
Sorry, I know this is a new requirement added after the fact. I realize that can be frustrating. This didn't occur to me earlier =/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added a
crc32.ChecksumIEEE
func call for hashing and made some changes for distributing SNIs per masquerade.