CURLOPT_SSH_*_KEYFILE: used for setting up, then no more

[bagder]

So changing them after the connection is made still allows libcurl to reuse the existing connections.

[Copilot]

Pull request overview

Updates libcurl SSH keyfile option documentation to clarify that CURLOPT_SSH_PUBLIC_KEYFILE and CURLOPT_SSH_PRIVATE_KEYFILE are only consulted when establishing a new SSH connection, and that changing these options after a connection is established does not prevent libcurl from reusing an already-vetted connection.

Changes:

• Document that CURLOPT_SSH_PUBLIC_KEYFILE is used only during new SSH connection setup; established connections may be reused even if the option changes.
• Document the same “setup-only” semantics for CURLOPT_SSH_PRIVATE_KEYFILE.
• Minor formatting adjustment in the private keyfile option text.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
docs/libcurl/opts/CURLOPT_SSH_PUBLIC_KEYFILE.md	Adds clarification that the public keyfile option is only used when setting up new SSH connections and does not affect reuse of already-established connections.
docs/libcurl/opts/CURLOPT_SSH_PRIVATE_KEYFILE.md	Adds the same connection-setup-only clarification for the private keyfile option and tweaks a paragraph’s formatting.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.