jss

#3 JSS has wrong encoding for ecdsa with sha* AlgorithmIdentifier
Closed Opened by cfu.

Closed
Reopen Issue

Investigation reveals that the issue described in the following ticket occurred in JSS:
https://pagure.io/dogtagpki/issue/1741 ECDSA Certificates Generated by Certificate System fail NIST validation test with parameter field.

Metadata Update from @cfu:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1547802
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mharmsen:
- Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1547802)
- Issue assigned to cfu

Metadata Update from @cfu:
- Assignee reset
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1575725

Metadata Update from @cfu:
- Issue assigned to cfu

commit a8e371e54b009159e9e3a0d198bd5eb3ed68ac22 (HEAD -> master, origin/master, origin/HEAD, ticket-3-AlgId)
Author: Christina Fu cfu@redhat.com
Date: Tue May 15 14:58:07 2018 -0700

Ticket 3 JSS has wrong encoding for ecdsa with sha* AlgorithmIdentifier
This ticket addresses the issue to meet RFC 5758 where param field must be omitted
in the ECDSA Signature algorithm' AlgorithmIdentifier for
ecdsa-withSHA224, ecdsa-with-SHA256, ecdsa-with-SHA384, or ecdsa-with-SHA512.
fixes https://pagure.io/jss/issue/3

Metadata Update from @cfu:
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to jss-4.4.2-10.fc27

Metadata Update from @mharmsen:
- Issue set to the milestone: 4.4.2
Metadata
None
None
None
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.