Skip to content

Allowing agent to skip unimplemented key types. - #134

Closed
pnabutovsky wants to merge 1 commit into
net-ssh:masterfrom
pnabutovsky:unsupported-key-type
Closed

Allowing agent to skip unimplemented key types.#134
pnabutovsky wants to merge 1 commit into
net-ssh:masterfrom
pnabutovsky:unsupported-key-type

Conversation

@pnabutovsky

Copy link
Copy Markdown

When net-ssh reads keys from the SSH agent it breaks when it encounters an unknown key type. Since the library does not implement certified RSA keys this is somewhat noticeable. The pull request is by no means a fix: the real solution is to implement the cert keys. I recognize that with my patch the agent will fail almost-silently, but I consider that the lesser of two evils.

bobveznat added a commit to bobveznat/net-ssh that referenced this pull request Jan 21, 2014
This does not implement certificate based authentication (described here
http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/PROTOCOL.certkeys?rev=HEAD)
but instead makes it so that if the certificate is not needed for
authentication net-ssh doesn't cause the entire application to die.

The net-ssh test suite continues to pass. On my own machine I did tests
with certificates loaded and verified that although authentication could
not proceed to a host requiring a certificate it at least did not die.

I also verified that I can continue to use normal rsa and dsa keys to
ssh to hosts that do not require certificates even when the certificates
are loaded into my ssh-agent instance.

This is a potential solution to issue net-ssh#124 and an alternative to the one
presented in pull request net-ssh#134.
@delano

delano commented Feb 1, 2014

Copy link
Copy Markdown
Collaborator

Thanks for looking into this. I decided to go with the solution in #142 as it didn't change current functionality.

@delano delano closed this Feb 1, 2014
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

Successfully merging this pull request may close these issues.

2 participants