Closed
Bug 123069
Opened 23 years ago
Closed 22 years ago
Mozilla ignores "encrypt always" preference!
Categories
(MailNews Core :: Security: S/MIME, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
psm2.2
People
(Reporter: KaiE, Assigned: KaiE)
References
Details
Attachments
(1 file)
3.27 KB,
patch
|
javi
:
review+
mscott
:
superreview+
asa
:
approval+
|
Details | Diff | Splinter Review |
Make sure you have certificates and mailnews configured. Configure to always sign and always encrypt. Close and restart Mozilla. Compose a message. Enter a recipient subject and body text. Do NOT open the security menu. Just send the message. Actual behaviour: Message is NOT sent encrypted. Could have to do with my NSS 3.4 build.
Comment 1•23 years ago
|
||
Let me try we my build (a bit stale - 2 days).
Comment 2•23 years ago
|
||
Tried with mozilla-win32-nss34-20020128-115010.zip, and I am not able to send the message. It complained it can't find the recipient encrypting cert. (I am sure I have the recipient cert in "Other People's" and it is verified to have the following usage: Email Recipient Certificate)
Comment 3•23 years ago
|
||
Antonio. You may have hit the bug whereby you must have sent yourself a signed email in order to be able to send an encrypted email where you are on the recipient list.
Assignee: ssaux → kaie
Priority: -- → P1
Target Milestone: --- → 2.2
Comment 4•23 years ago
|
||
For my last comment #2, I didn't send the message to myself, but to other recipient. But anyway, I am still hitting the same problem described in bug 122933 using the latest NSS 3.4 build (20020201).
Assignee | ||
Comment 5•23 years ago
|
||
I retested with my latest build. I still see this bug as originally described. Encryption is not used unless you manually open the Options/Security menu in composer before sending.
Status: NEW → ASSIGNED
Assignee | ||
Comment 6•23 years ago
|
||
In case the menu has not been used, we query the wrong preference...
Assignee | ||
Comment 7•23 years ago
|
||
Javi, can you please review?
Comment 8•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
Comment 9•23 years ago
|
||
Comment on attachment 68667 [details] [diff] [review] Suggested fix r=javi
Attachment #68667 -
Flags: review+
Assignee | ||
Comment 10•23 years ago
|
||
Scott, can you please sr ?
Comment 11•22 years ago
|
||
Comment on attachment 68667 [details] [diff] [review] Suggested fix sr=mscott
Attachment #68667 -
Flags: superreview+
Comment 12•22 years ago
|
||
Comment on attachment 68667 [details] [diff] [review] Suggested fix a=asa (on behalf of drivers) for checkin to the 1.0 trunk
Attachment #68667 -
Flags: approval+
Assignee | ||
Comment 13•22 years ago
|
||
checked in, fixed.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•