1115566 - Unable to get a certificate (imap, smtp)

Status: RESOLVED FIXED

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Woody Suwalski]

Attachment: The 2.31 dialog box

User Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31
Build ID: 20141202221108

Steps to reproduce:

Starting with 2.31 the Seamonkey is unable to get an imap (nor smtp) certificate from an imap server, and as a result I can not use "Confirm Security Exception" button.


Actual results:

Message "Unable to obtain identification status for the given site".
The "Conform Security Exception" button greyed out.


Expected results:

In 2.30 and earlier I see a "View..." button, and can confirm that the self-signed cert is OK.

Comment 1

[Woody Suwalski]

Attachment: The 2.30 dialog box enabling to Confirm Security Exception

Comment 2

[Woody Suwalski]

Same problem present in 2.32b2

Comment 3

[Woody Suwalski]

And it is not fixed in 2.32b3... 8-(

Comment 4

[Woody Suwalski]

Also broken in 2.32
It is unable to "Get Certificate" - the button is not doing anything ...
As a result I can not "View" nor "Confirm Security Exception"

Comment 5

[Woody Suwalski]

Upgraded to critical, as all mail subsystem is not functional.

Comment 6

[Edmund Wong (:ewong)]

I'm seeing this as well.

In the Error Console, I see the following errors:

Timestamp: 1/23/2015 3:22:35 PM
Error: mail_server_ip:143 uses an invalid security certificate.

The certificate is not trusted because no issuer chain was provided.
The certificate is only valid for mail_server_ip

(Error code: sec_error_unknown_issuer)

Timestamp: 1/23/2015 3:22:35 PM
Error: Attempted to connect to a site with a bad certificate in the add exception dialog. This results in a (mostly harmless) exception being thrown. Logged for information purposes only: [Exception... "Establishing a connection to an unsafe or otherwise banned port was prohibited"  nsresult: "0x804b0013 (NS_ERROR_PORT_ACCESS_NOT_ALLOWED)"  location: "JS frame :: chrome://pippki/content/exceptionDialog.js :: checkCert :: line 109"  data: no]
Source File: chrome://pippki/content/exceptionDialog.js
Line: 115

Comment 7

[Michal Žejdl]

Import server cert via manager doesn't help. The same exceptionDialog pops up.

Setting network.security.ports.banned.override to "143" in about:config changes error message in JS console to "ssl_error_rx_record_too_long".

Comment 8

[Woody Suwalski]

Problem present in 2.32.1

Comment 9

[Woody Suwalski]

Same problem in 2.33b1

Comment 10

[Woody Suwalski]

I have started copying to the .mozilla/seamonkey/salt/ directory the cert_override.txt file from a 2.31 seamonkey installation, that seems to be enough to permit the connection. So basically the method to create the cert_override.txt file is missing in 2.32 / 2.33

Comment 11

[Philip Chee]

WAG: Try backing out the three patches in https://bugzilla.mozilla.org/show_bug.cgi?id=1085509#c24

Comment 12

[[e-mail]]

Whoops, this is my fault.

I fixed bug 1059476 for SeaMonkey 2.31, and uplifted it to 2.30, but there was a typo in it; I pushed a typo fix but only in the 2.30 branch so 2.31 and later don't have the fix :-(

Comment 13

[[e-mail]]

http://hg.mozilla.org/releases/comm-beta/rev/673ba79dc3f4 is the typo fix that needs to be landed on trunk and all branches.

Comment 14

[Edmund Wong (:ewong)]

Attachment: patch from releases/comm-beta/rev/673ba79dc3f4

Comment 15

[Edmund Wong (:ewong)]

Comment on attachment 8642212 [details] [diff] [review]
patch from releases/comm-beta/rev/673ba79dc3f4

[Approval Request Comment]
Regression caused by (bug #): 1059476
User impact if declined: cannot get certificate in imap/smtp
Testing completed (on m-c, etc.): 
Risk to taking this patch (and alternatives if risky): none
String changes made by this patch: none

Comment 16

[Ian Neal]

Comment on attachment 8642212 [details] [diff] [review]
patch from releases/comm-beta/rev/673ba79dc3f4

[Triage Comment]
r=me and a=me for all branches (including esr38 if needed) and for CLOSED TREE

Comment 17

[Edmund Wong (:ewong)]

Comment on attachment 8642212 [details] [diff] [review]
patch from releases/comm-beta/rev/673ba79dc3f4

Pushed to comm-central:
 https://hg.mozilla.org/comm-central/rev/eace0c64cb12

Pushed to comm-aurora:
 https://hg.mozilla.org/releases/comm-aurora/rev/0d0cb49c8208

Pushed to comm-beta:
 https://hg.mozilla.org/releases/comm-beta/rev/4633d2d32b19

Pushed to comm-release:
 https://hg.mozilla.org/releases/comm-release/rev/3b2a878de79b

Comment 18

[Philip Chee]

Pushed to comm-release SEAMONKEY_2_35_RELEASE_BRANCH
http://hg.mozilla.org/releases/comm-release/rev/ded408137138

Comment 19

[Woody Suwalski]

Seems working OK on 2.35 Seamonkey