Skip to content
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

Support for new OpenSSH 6.5+ private key format #618

Closed
wants to merge 10 commits into from

Conversation

mchlt
Copy link

@mchlt mchlt commented Nov 10, 2015

Added support for new OpenSSH 6.5+ private key format. See issue #602.
This code only adds the ability to READ that key format, not write it.

I could only test the keys on one box as I found that my Solaris, Raspberry pi and Oracle Linux boxes all still have older versions of SSH. So only tested this on Ubuntu 15 against OpenSSH_6.9p1.

Figuring out the actual format and which blob was which key was quite the puzzle, it's not really documented completely anywhere.

As discussed previously, this does add a dependency on py-bcrypt 0.4
The cryptography module does not have bcrypt, nor the required bcrypt_pbkdf function (which is similar, but not quite the same as pbkdf2...)

@cjac
Copy link

@cjac cjac commented Mar 31, 2016

Have you, in your wanderings through this code, found a way to identify the Public Key Algorithm of a given private key file? Or even the content of that file would work.

jaredhobbs added a commit to carta/paramiko that referenced this issue Nov 28, 2018
This work is based off the work done in paramiko#618
ploxiln pushed a commit to ploxiln/paramiko-ng that referenced this issue May 2, 2019
based off work by Michiel Tiller <michiel@tiller.nl>
from paramiko#618
ploxiln pushed a commit to ploxiln/paramiko-ng that referenced this issue May 5, 2019
based off work by Michiel Tiller <michiel@tiller.nl>
from paramiko#618
ploxiln pushed a commit to ploxiln/paramiko-ng that referenced this issue May 23, 2019
based off work by Michiel Tiller <michiel@tiller.nl>
from paramiko#618
@XVilka

This comment was marked as disruptive content.

@bitprophet
Copy link
Member

@bitprophet bitprophet commented Dec 3, 2019

Rolling into #1343 as noted.

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.

None yet

4 participants