Bug 2106043
| Summary: | [RFE] PKINIT: support elliptic curve cryptography [rhel-9] | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Julien Rische <jrische> | |
| Component: | krb5 | Assignee: | Julien Rische <jrische> | |
| Status: | CLOSED MIGRATED | QA Contact: | Michal Polovka <mpolovka> | |
| Severity: | unspecified | Docs Contact: | Filip Hanzelka <fhanzelk> | |
| Priority: | unspecified | |||
| Version: | 9.1 | CC: | abobrov, fhanzelk, frenaud, ftrivino, gfialova | |
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA, Triaged | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Known Issue | ||
| Doc Text: |
.MIT Kerberos does not support ECC certificates for PKINIT
MIT Kerberos does not implement the RFC5349 request for comments document, which describes the design of elliptic-curve cryptography (ECC) support in Public Key Cryptography for initial authentication (PKINIT). Consequently, the MIT `krb5-pkinit` package, used by RHEL, does not support ECC certificates. For more information, see link:https://www.rfc-editor.org/rfc/rfc5349.html[Elliptic Curve Cryptography (ECC) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)].
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2214326 (view as bug list) | Environment: | ||
| Last Closed: | 2023-09-18 19:55:39 UTC | Type: | Story | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 2077450 | |||
| Bug Blocks: | 2214326 | |||
|
Description
Julien Rische
2022-07-11 15:24:09 UTC
*** Bug 2125392 has been marked as a duplicate of this bug. *** *** Bug 2106039 has been marked as a duplicate of this bug. *** Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |