Closed Bug 108594 Opened 24 years ago Closed 24 years ago

[S/MIME] Do not import own encryption cert in db

Categories

(MailNews Core :: Security: S/MIME, defect, P1)

Product:
MailNews Core
Component:
Security: S/MIME
Version:
1.0 Branch
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
psm2.2

People

(Reporter: ssaux, Assigned: ddrinan0264)

References

Details

If you open an encrypted email where you're on the cc list, your own encryption cert gets copied in the db and that copy cannot be deleted. To reproduce: Have your own certs on a hardware device in a new profile. Send yourself an encrypted email. Remove your hardware token. Look at your certs In the your certs tabs, the encryption cert is present, but you can't delete it.
Priority: -- → P1
Target Milestone: --- → 2.2
Component: Client Library → S/MIME
QA Contact: junruh → alam
Blocks: 74157
S/MIME bugs are automatically nsbeta1 candidates. (this is a bulk update - there may be some adjustment of the list).
Keywords: nsbeta1
Keywords: nsbeta1+
wfm
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
QA Contact: alam → carosendahl
Stephane, any way I can get a reader and token card? Can't verify these types of bugs without it. Thanks, /c
verified
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → MailNews Core
QA Contact: carosendahl → s.mime
You need to log in before you can comment on or make changes to this bug.