Bug 999078 - NSS provide ECC smime functionality
Summary: NSS provide ECC smime functionality
Keywords:
Status: CLOSED DUPLICATE of bug 752980
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nss
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Elio Maldonado Batiz
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: ecc
TreeView+ depends on / blocked
 
Reported: 2013-08-20 17:34 UTC by Jack Magne
Modified: 2013-11-04 15:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-04 15:34:33 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jack Magne 2013-08-20 17:34:09 UTC
Description of problem:

Currently NSS does not have SMIME support for ECC certificates. Having this support would allow the creation of SMIME encrypted and signed emails using products such as Thunderbird.


Version-Release number of selected component (if applicable):

latest


How reproducible:

Every time.


Steps to Reproduce:
1. Attempt to create a signed and encrypted email in TBird with an ECC cert



Actual results:

The process will fail, most notably when trying to select a suitable ECC certificate for encryption.

Expected results:

We should be able to create signed and encrypted emails with TBird or other NSS supported email clients. Especially support for ECC smart cards is desirable.


Additional info:

Currently there exists a collection of 3rd party community patches that suports this functionality. I have myself tested these and gotten themt o work. I imagine the thrust of this bug would be to review and deploy some combination of these patches.

Comment 6 Kai Engert (:kaie) (inactive account) 2013-11-04 15:34:33 UTC
Marking as a duplicate of bug 752980 which should have fixed this issue - although we no longer ship Thunderbird in RHEL 7, support for this would have to be confirmed using NSS command line utilities, or the evolution mail client.

*** This bug has been marked as a duplicate of bug 752980 ***


Note You need to log in before you can comment on or make changes to this bug.