-
Notifications
You must be signed in to change notification settings - Fork 790
pkg/driver/vz: Try SSH handshake to check if SSH port is available. #4337
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
Closed
norio-nomura
wants to merge
2
commits into
lima-vm:master
from
norio-nomura:vz-ssh-over-vsock-try-handshake
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
It is quite hard to maintain the code that mixes up
/usr/bin/sshwithgolang.org/x/crypto/sshThere 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.
The PR looks overengineering.
Can we consider another way to fix the issue #4334 ?
e.g., by writing vsock availability to a serial port
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.
What I really want to do is #4333, and this is like a grounding.
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 feel that #4333 and this can also be implemented without using host key generation and
known_hosts.If the host key generation and the
known_hostsarea disappear, I think the implementation will be simpler.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 tried to reconsider this, but I think it's difficult.
On Fedora 43's case:
systemdlistens toVSOCK:22.Accepted connection is denied by some mechanism(audit?).
port availability detection log:
Actual log on SSH connection via forwarded to VSOCK is denied:
To writing availability via serial:
So, I think, it is more reliable to actually try the connection with the SSH protocol, and the portability is also high.
And using
sshinstalled on the host to test the connection to VSOCK will increase the same uncertainty as the execution of requirements that cause CI failure.Uh oh!
There was an error while loading. Please reload this page.
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.
Why can
crypto/sshavoid that uncertainty?Can we just fix that uncertainty by executing
/usr/bin/sshwith some option?Uh oh!
There was an error while loading. Please reload this page.
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.
Because
x/crpyto/sshdoes not use inter-process communication.I think
stderr=\"\": read |0: bad file descriptor"that I'm trying to fix in #4333 is an error in pipe used for inter-process communication. I don't think it can be fixed with the option to pass to/usr/bin/ssh.It might be fixed if the executing method of
/usr/bin/sshchanges, but it seemed better to reduce external dependencies at the run time.After trying #4333 and #4337 so far, I thought
x/crypto/sshwould be reliable enough to execute requirements.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.
limactl shelldefinitely depends on/usr/bin/sshthoughThere 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.
It can also be implemented in
x/crypto/ssh. There's no reason for us to do that.All SSH communication doesn't have to depend on either
/usr/bin/sshorx/crypto/ssh.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.
Lima still has to generate
~/.lima/INST/ssh.configfor interoperability with external programs, and has to verify that the generated config works, regardless to thelimactl shellimplementation uses it or not.