Hi,
I would like to use sshx in a setup, where the actions workflow output is public. Simply outputting the generated URL of sshx is therefore not really an option.
So now, the question is how to deal with this scenario?
A viable approach would be if we could add a parameter to sshx, where the cryptographic token (the one that is already used to secure the sshx connection) can be taken from stdin instead of being generated by sshx itself.
This would allow to store the secret as a pre-defined secret variable in the actions runner and therefore have a predictable URL, which I could bookmark once and always have access to the sshx session without having the URL in the public log.
While this sounds relatively straightforward, the token would be then potentially identical for multiple sshx clients that try to connect the server. I am not sure how the sshx server would handle this.
What do you think? Is this a direction where one could go forward?
cheers,
lemoer
Hi,
I would like to use sshx in a setup, where the actions workflow output is public. Simply outputting the generated URL of sshx is therefore not really an option.
So now, the question is how to deal with this scenario?
A viable approach would be if we could add a parameter to sshx, where the cryptographic token (the one that is already used to secure the sshx connection) can be taken from stdin instead of being generated by sshx itself.
This would allow to store the secret as a pre-defined secret variable in the actions runner and therefore have a predictable URL, which I could bookmark once and always have access to the sshx session without having the URL in the public log.
While this sounds relatively straightforward, the token would be then potentially identical for multiple sshx clients that try to connect the server. I am not sure how the sshx server would handle this.
What do you think? Is this a direction where one could go forward?
cheers,
lemoer