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
Need ECC-specific Enrollment Profiles for standard conformance #3068
Comments
Comment from cfu (@cfu) at 2018-03-01 18:16:49 Metadata Update from @cfu:
|
Comment from mharmsen (@mharmsen) at 2018-03-01 19:04:15 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2018-03-06 14:35:16 Metadata Update from @mharmsen:
|
Comment from cfu (@cfu) at 2018-03-12 18:04:25 commit 27cf99e
|
Comment from cfu (@cfu) at 2018-03-12 18:04:26 Metadata Update from @cfu:
|
Comment from cfu (@cfu) at 2018-03-12 18:06:06 just for the record: |
Comment from mharmsen (@mharmsen) at 2018-03-28 21:24:41 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2018-04-05 18:02:44 commit 9956821
|
Comment from mharmsen (@mharmsen) at 2018-04-10 20:57:46 Metadata Update from @mharmsen:
|
This issue was migrated from Pagure Issue #2950. Originally filed by cfu (@cfu) on 2018-03-01 18:13:46:
Currently many of the enrollment profiles are shared between RSA and ECC certificates. As such the keyUsage extension is not conforming.
This task is to add needed ECC-specific enrollment profiles and make needed adjustments to existing ones for standard conformance.
The text was updated successfully, but these errors were encountered: