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.

Sign up for GitHub

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

Jump to bottom

java.security.NoSuchAlgorithmException: no such algorithm: OID.1.2.840.113549.1.1.12 for provider Mozilla-JSS when signing a CSR using SHA384withRSA #2466

Closed
pki-bot opened this issue Oct 3, 2020 · 4 comments
Closed

java.security.NoSuchAlgorithmException: no such algorithm: OID.1.2.840.113549.1.1.12 for provider Mozilla-JSS when signing a CSR using SHA384withRSA #2466

pki-bot opened this issue Oct 3, 2020 · 4 comments
Labels
Closed: Fixed
Milestone
10.3.3

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #2346. Originally filed by dminnich (@dminnich) on 2016-06-02 19:59:33:

  • Closed as Fixed
  • Assigned to cfu (@cfu)

An embedded device is spitting out CSRs that use sha384WithRSAEncryption. We can't reconfigure it to use SHA512RSA or EC anything. We also can't generate a key and cert pair and upload it to the device.

Try to sign

-----BEGIN CERTIFICATE REQUEST-----
MIIDBDCCAewCAQAwgZkxCzAJBgNVBAYTAk5DMRAwDgYDVQQIDAdSYWxlaWdoMR8w
HQYDVQQHDBZJbmZvcm1hdGlvbiBUZWNobm9sb2d5MRAwDgYDVQQKDAdSZWQgSGF0
MQ0wCwYDVQQLDARJbmMuMSMwIQYDVQQDDBpvdnBuMDEtbWdtdC5mYWIucmVkaGF0
LmNvbTERMA8GCSqGSIb3DQEJARYCVVMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw
ggEKAoIBAQCnFzNhnfslG//kD/31perhjI2muSuU66ameDXkspLjIxkBiC78Yhcr
Sg9u5mUXvDa74GWwoiO8EEbXQp/+ekS4BgBSFGrvY0uHZp4YVOOgfldzCg211HKM
CgG+IJ/QXMmTvrlwGxTGuTefxWinELV75hPNUvPk4wtLafpWfv2e1TIFTLR/EHUs
K8pO2dFy037HK3ELpip1xeRsaRoynjr8SG4yp2Hjkyd/iww/Yp4hINDgELjm0/QJ
5ReBcM/+kAzLBJsZv1mUC9CKXrED60J62rl754u9b1NZ/lBR8E/xNdd0jnK6LWRp
mIMcFRcicyxK5PiWaBh4a/uk/jBV74zHAgMBAAGgJTAjBgkqhkiG9w0BCQcxFgwU
QSBjaGFsbGVuZ2UgcGFzc3dvcmQwDQYJKoZIhvcNAQEMBQADggEBAGypMwHIQGjY
RUYjlSIxpGBO3f1wBRNPQrTHoX7iNF4K22OEA6d0hvGZDHI699R5uyZx3+aKiIlE
6N/iAenytWQmztpf7BEVVzKutW0kjJ2zz76HkuI6d1L3hc14WnCG6HtR09KaHsh9
eJJqKVfXgJLC0ZRjgkyS0XM7nfQgskSWB96J9r5WWxRX/ETV+vrq3j4N7+HspzFg
xO7rxaA6BJn/i3E/WgImirhfN+4d2cL2VORu7Lu0izdPahWuAnmezxbJjbCL6OY5
bZwU2WjRTlMbDg9M66GFvOENw7cua+FPr8zpzNe0pxC1n/4Q71kQNdqIBI/TC5e2
xMdh9hervRc=
-----END CERTIFICATE REQUEST-----

Get error in summary indicating that its not supported.
@pki-bot pki-bot added this to the 10.3.3 milestone Oct 3, 2020
@pki-bot pki-bot closed this as completed Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from dminnich (@dminnich) at 2016-06-02 20:00:45

uploaded CSR since ticket ate part of it.

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from dminnich (@dminnich) at 2016-06-02 20:07:38

attachment
bad.csr

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cfu (@cfu) at 2016-06-18 02:38:09

Tested to work with

  1. the CSR provided by bug reporter in ticket against caServerCert enrollment profile
  2. few selected profiles

Pushed to master

commit 158bb22
Author: Christina Fu cfu@redhat.com
Date: Fri Jun 17 15:18:52 2016 -0700

Ticket 2346 support SHA384withRSA
This patch adds support for SHA384withRSA signing algorithm.

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from dminnich (@dminnich) at 2017-02-27 14:03:55

Metadata Update from @dminnich:

  • Issue assigned to cfu
  • Issue set to the milestone: 10.3.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Closed: Fixed
Projects
None yet
Milestone
10.3.3
Development

No branches or pull requests
1 participant
@pki-bot