feat: Key parsing #294
Open
feat: Key parsing #294
Conversation
This file contains hidden or 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
|
The id_rsa key still needs to be converted to SSH2 format, but somehow the ssh-keygen conversion fails everytime. |
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.
The following PR implements a key parser, which serves different functionality:
[email protected]global requests #224Furthermore to add easy usage for inclusion of host and user keys into the SSH-Attacker, there was added the HostKeyPathsDelegate and UserKeyPathsDelegate, which implements the requirements of #179 , to specify host and user keys by CLI parameters. The parameter specification is done by a comma separated list.