Closed
Bug 124046
Opened 23 years ago
Closed 23 years ago
[LDAP] Implement cert fetching in addressing widget.
Categories
(MailNews Core :: Security: S/MIME, defect, P1)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 119394
psm2.2
People
(Reporter: ssaux, Assigned: ssaux)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
text/plain
|
Details |
As per the S/MIME specs.
I looked at addressingWidgetOverlay.xul, and adding a onblur attribute to the
msgRecipient#1 element would allow me to do the work needed to decide whether I
need to get the cert (and do it if needed).
Unfortunately adding the onblur att, and the corresponding handler in
addressingWidgetOverlay.{xul,js} would break the extension model.
So I created a new overlay, called addressingSMIMEOverlay.xul, in the smime ext
and I attempt to add the onblur attribute to the msgRecipient#1 element in it.
Unfortunately this doesn't seem to work.
I'll attach the new files.
Scott any idea?
Assignee | ||
Comment 1•23 years ago
|
||
Not a patch not for review.
Assignee | ||
Updated•23 years ago
|
Priority: -- → P1
Target Milestone: --- → 2.2
Assignee | ||
Comment 2•23 years ago
|
||
S/MIME bugs are automatically nsbeta1 candidates. (this is a bulk update - there
may be some adjustment of the list).
Keywords: nsbeta1
Assignee | ||
Updated•23 years ago
|
Updated•23 years ago
|
QA Contact: alam → carosendahl
Comment 3•23 years ago
|
||
Adding [LDAP] to subject line, marking as a regression from 4.7x.
In 4.7x, the error message indicates to check the security info. From there you
may fetch all of the needed certificates (provided the exist in the directory
server(s) configured) to continue sending.
Keywords: regression
Summary: Implement cert fetching in addressing widget. → [LDAP] Implement cert fetching in addressing widget.
Comment 4•23 years ago
|
||
I think this is a dupe.
*** This bug has been marked as a duplicate of 119394 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•