Handle SSH URIs with connection parameters #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h-scp-sftp-ssh-uri-04.txt
|
Some tests for good and bad syntax would be helpful. |
karenetheridge
force-pushed
the
master
branch
from
5dcfddf
to
3a2965a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SSH URIs as described on the RFC draft http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri-04 admit a set of c-param components that can be used to pass additional information about the connection (i.e., the key to be used).
This patch extends URI to support it.
URIs of class URI::ssh now have a c_params method accepting/returning an array with the c-param components.