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

Feature request: SSL Private/Public key in memory instead of file #2310

Closed
MonkeybreadSoftware opened this Issue Feb 13, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@MonkeybreadSoftware
Contributor

MonkeybreadSoftware commented Feb 13, 2018

Hi,

you can specify the private and public keys for SSH/SSL as file paths.
We'd like to avoid with LibCURL to write them to a file and just pass them as data blob or text encoded.

SSLCERT, SSH_PUBLIC_KEYFILE and SSH_PRIVATE_KEYFILE all with _Text or so option.
Could this be added?

@bagder

This comment has been minimized.

Member

bagder commented Feb 13, 2018

  1. This is not a bug or a problem but a feature-request, and we don't track them here. This issue will be closed soon.
  2. It's just code so it can certainly be done. There are probably a lot of challenges to do that (nicely) though, since we have many different TLS back-ends and two SSH back-ends, and some of them might be easy and some might offer resistance.

@bagder bagder closed this in a3e52a7 Feb 18, 2018

@bagder

This comment has been minimized.

Member

bagder commented Feb 18, 2018

Now listed in the TODO: here.

fsedano added a commit to fsedano/curl that referenced this issue Feb 20, 2018

TODO: "Support in-memory certs/ca certs/keys"
removed SSLKEYLOGFILE support (fixed)

removed "consider SSL patches" (outdated)

Closes curl#2310

@lock lock bot locked as resolved and limited conversation to collaborators May 19, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.