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

Export pk8 file from keystore #274

Closed
timea-techgirl opened this issue May 26, 2021 · 6 comments
Closed

Export pk8 file from keystore #274

timea-techgirl opened this issue May 26, 2021 · 6 comments

Comments

@timea-techgirl
Copy link

Is your feature request related to a problem? Please describe.
Can't export private key in pk8 format

Describe the solution you'd like
An option to export private key in pk8 format

Describe alternatives you've considered
I used openssl to generate it

@kaikramer
Copy link
Owner

@timea-techgirl
Copy link
Author

timea-techgirl commented May 27, 2021

I just checked, still couldn't find how to export in pk8 format.

Need to get a certificate.pem and key.pk8,
http://www.londatiga.net/it/how-to-sign-apk-zip-files/

@kaikramer
Copy link
Owner

The section in the manual is called "To export a Key Pair's private key as PKCS #8". Here is a short extract:

  • Right-click on the Key Pair entry in the KeyStore Entries table. Select the Export sub-menu from the pop-up menu and from there choose Export Private Key.
  • Select the PKCS When opening keystore the alias is not displayed correctly #8 radio button and press the OK button.
  • Uncheck the Encrypt check box.
  • (Do not check the PEM check box.)
  • Use the Browse button to select an export file.

@timea-techgirl
Copy link
Author

@kaikramer Thank you. I tried this before and didn't export it because the extension didn't automatically change from pcks8 to pk8. I noticed extensions changing automatically when I selected other options. But here, it remained the same. :) Hope that can be polished.

@kaikramer
Copy link
Owner

Ah, now I understand... The file extension has no effect or meaning for PKCS#8 files, however. There is no commonly accepted standard or best practice for naming PKCS#8 files. You can name the file however you like.

In the linked guide .pk8 was used, but that is completely arbitrary. For comparison: A question about converting a key to PKCS#8 with OpenSSL on Stackoverflow, where someone used the extension .pkcs8.pem and someone else used .key.

What matters is the actual format of the file content and KSE produces the same output format as OpenSSL.

Anyway, any user feedback is appreciated!

@timea-techgirl
Copy link
Author

Oh I see, I saw many formats too for certificates and key files. It will be confusing for beginners.

To reduce the confusion, what about a dropdown list to choose among known formats? This would make us understand that it can be saved in various formats.

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

No branches or pull requests

2 participants