Skip to content
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

Allow specification of trusted certificates / CAs #31

Open
reg0bs opened this issue Nov 7, 2023 · 2 comments
Open

Allow specification of trusted certificates / CAs #31

reg0bs opened this issue Nov 7, 2023 · 2 comments

Comments

@reg0bs
Copy link

reg0bs commented Nov 7, 2023

First and foremost: Thanks for sharing sshx and huge respect for what you've built here!

I'm running my own sshx server and it gets a certificate by an internal (private) CA. This leads to the sshx client not accepting the cert, because it seems it brings a list of CAs with it using a rust package.

So, it would be nice to be able to specify a file or folder with certificates of CAs (aka trust store) that should be trusted by the sshx client additionally or instead of the ones included, similar to the --cacert option in curl or many others.

Thanks!

@shumvgolove
Copy link

Hey!

While this would be great addition, in the meantime you could recompile sshx binary with tls-roots feature, which will lookup OS ca-bundles following sshx setup section here: #27

@ekzhang
Copy link
Owner

ekzhang commented Nov 7, 2023

Thank you for the suggestion! It's really helpful to know more about how you'd like to use it.

I might not get to this for a while -- officially, only the sshx.io server cluster that I maintain is supported for the time being. That one uses public CAs, hence the bundling of Mozilla's webpki-roots list. Trying to make this rock-solid first!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants