-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat(landscape): Implement support for SSL certificates in Landscape connection #320
Conversation
d360c61
to
333f76c
Compare
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.
Excellent work!
I do have some changes to request, to ensure we don’t silently fallback to insecure mode (let’s say that you have a service that accept both, you will then trust it for an invalid configuration).
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.
Looking good! Thanks for this :)
We need to modify the config on WSL's side because it'll need access to wslpath once we implement support for the ssl certificate.
The mocked "cmd.exe echo %LocalAppData%" would return a Linux path, and then the mocked "wslpath" would do nothing. Of course, this is not accurate, as cmd.exe returns always the Windows path. This is here fixed.
f7cc18a
to
9b04178
Compare
Force-pushed to rebase main and squashed fixups, no changes to code. |
Three changes in this PR:
computer_name
override took place in the agent, when creating the task. This is now moved to the WSL Pro Service.computer_name
, the WSL Pro Service will now also rewritessl_public_key
so that it is converted from Windows path to WSL path. This step is skipped if this key is not present.ssl_public_key
when available. This key will be used to secure the connection to the Hostagent server.UDENG-1544