-
Notifications
You must be signed in to change notification settings - Fork 44
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
"no key" error while loading proxy certificate with -----BEGIN PRIVATE KEY----- prefix #146
Comments
👍 |
According to http://www.cryptosys.net/pki/rsakeyformats.html |
Whereas one is encrypted and one is unencrypted. |
👍 |
I had same issue with private keys generated using openssl 1.0 and created workaround, see #118 |
tzok
added a commit
to tzok/JGlobus
that referenced
this issue
Oct 22, 2015
This is a fork of JGlobus which fixes the following issues: jglobus#118 jglobus#146 Patch provided by https://github.com/vokac
ellert
added a commit
to ellert/JGlobus
that referenced
this issue
Oct 30, 2018
Fixes the following issues: * jglobus#118 * jglobus#146 Merge remote-tracking branch 'vokac/master' into PKCS8-key-format
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
voms-proxy-init version 3.0.3 generates proxy certificate with
-----BEGIN PRIVATE KEY-----
and-----END PRIVATE KEY-----
prefix and postfix which is not recognized byorg.globus.gsi.X509Credential.load(InputStream)
. Cutrrently onlyBEGIN RSA PRIVATE KEY
sequence is supported.The text was updated successfully, but these errors were encountered: