Pass ServerName in the ConnInfo packet #9
Merged
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.
To easy the process of selecting the correct TLS certificate for the incoming connection on the Elastic Agent side a unique ServerName will be generated per spawned applications. When that client connects back to the Elastic Agent with that ServerName the matching certificate will be required on the Elastic Agent side and be verified.
This means to connect back to Elastic Agent you need 5 things for it to accept the connection:
The unique token is not used as the ServerName because I want to ensure that is always encrypted and in a verified connection before it is sent back.