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

Option for providing client TLS certificate #40

Open
ghost opened this issue Nov 14, 2018 · 6 comments
Open

Option for providing client TLS certificate #40

ghost opened this issue Nov 14, 2018 · 6 comments

Comments

@ghost
Copy link

ghost commented Nov 14, 2018

Please implement an option to provide the client's TSL certificate. Currently you need a proxy server like stunnel/haproxy to provide the certificate if the server verifies it.

@MikeTaylor
Copy link
Contributor

This is by design. YAZ is a Z39.50 toolkit, not a web server. We could keep adding features and features to it, until it contains an email reader and (in accordance with Greenspun's tenth rule), an ad-hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp. But we prefer the Unix philosophy of keeping each tool small and clean, doing one thing well. haproxy is a fine tool for supporting TLS.

@ghost
Copy link
Author

ghost commented Nov 14, 2018

But the support is there, since yaz-client allows you to connect to TLS servers (By prefixing the URL with ssl:) but it apparently uses a static TLS cert.

@MikeTaylor MikeTaylor reopened this Nov 14, 2018
@MikeTaylor
Copy link
Contributor

Thanks for spotting that. I have re-opened the issue, and will leave to to @adamdickmeiss to comment.

@adamdickmeiss
Copy link
Contributor

Yes. Seems like a good idea.. Like -E option for curl and --certificate option for wget.

@ghost
Copy link
Author

ghost commented Nov 15, 2018

So is this going to be implemented only in the CLI or in the library as well?

@adamdickmeiss
Copy link
Contributor

adamdickmeiss commented Nov 15, 2018

Library including the ZOOM API.

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

No branches or pull requests

2 participants