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
Implement cockpit tunelling using system ssh #65
Conversation
@mvollmer Hi, we're in the progress of switching over from |
(Upps, missed this. I'll check this out.) |
@adamruzicka, this looks good to me. I would have to run it to find any bugs... :-) The point of using net/ssh for this when this was written was to replicate the exact behavior of remote execution of batch commands. E.g., the Cockpit tunnel should use the exact same authentication parameters as batch rex. So if batch rex switches over to /bin/ssh and you have it all figured out there, then the Cockpit tunnel code should just do the same things regarding options and passwords, etc. In other words, don't try hard to preserve the current behavior, but try to keep it in synch with batch rex. Thanks! |
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.
Thanks @adamruzicka, good job on this one
It seems like even with this, the cockpit session fails with authentication error. It may be caused by something else, since pure REX job seems to work. The target system is Fedora 35. It seems to work against Debian, however there it fails with internal server error on the cockpit side. Debian has cockpit-system 239, Fedora 35 has 259. |
And the same on Fedora 34 (cockpit-system 255) |
And interestingly enough, the SSH connection seems to be successful based on the log from the target machine
|
No description provided.