441863 - Missing Add exception link or button

Status: RESOLVED WORKSFORME

(Core :: Security: PSM, defect)

Description

[Peter Santiago]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

I am using a gateway distro (CLarkconnect), while trying to access the admin web page, Firefox 3 reports the error

192.168.1.1:81 uses an invalid security certificate.

The certificate is not trusted because it is self signed.
The certificate is only valid for <a id="cert_domain_link" title="kechara.psinergybbs.com">kechara.psinergybbs.com</a>

(Error code: sec_error_untrusted_issuer)

No Add exception link or button can be found.

Reproducible: Always

Steps to Reproduce:
1. Visit Admin web console
2. Cannot access site

Actual Results:  
192.168.1.1:81 uses an invalid security certificate.

The certificate is not trusted because it is self signed.
The certificate is only valid for <a id="cert_domain_link" title="kechara.psinergybbs.com">kechara.psinergybbs.com</a>

(Error code: sec_error_untrusted_issuer)


Expected Results:  
Add Exception link should come up or show p

Comment 1

[Peter Santiago]

Attachment: Error page ... Add Exception Link or button missing

Comment 2

[Johnathan Nightingale [:johnath]]

This screencap is very strange - some of the strings are different than they should be (the title of the error page is "Secure Connection Failed", but you are getting the default "Cannot Complete Request" language instead) and you aren't seeing the hyperlinking you should.

It looks like our error page is being passed the wrong error code.

I'm going to move this over to the right component, but in the meantime, can you try this for me?  Load up the page that gives you the error again (assuming it isn't a one-time thing, and you can reproduce it) and then type this into the location bar:

javascript:alert(document.documentURI);

When you hit enter, it should popup a very wordy dialog that shows us what arguments are being passed to the error page, and would be helpful information to have.

Comment 3

[Jean-Yves Perrier [:teoli]]

We have noticed that on one users on the forum in french ( http://www.geckozone.org/forum ). If I remember well, a new profile cured the problem. I can look again for the message to confirm, if needed.

Comment 4

[Jean-Yves Perrier [:teoli]]

Sorry for the spam: I found the case again: http://www.geckozone.org/forum/viewtopic.php?t=66582 (there are some screen copies in it)

The cause of the invalidity of the cert was different (not issued for the right site), but the symptom (some <a in the message) was the same.

Safe-mode didn't cure the problem, but a new profile yes.

Comment 5

[Peter Santiago]

(In reply to comment #2)
> This screencap is very strange - some of the strings are different than they
> should be (the title of the error page is "Secure Connection Failed", but you
> are getting the default "Cannot Complete Request" language instead) and you
> aren't seeing the hyperlinking you should.
> 
> It looks like our error page is being passed the wrong error code.
> 
> I'm going to move this over to the right component, but in the meantime, can
> you try this for me?  Load up the page that gives you the error again (assuming
> it isn't a one-time thing, and you can reproduce it) and then type this into
> the location bar:
> 
> javascript:alert(document.documentURI);
> 
> When you hit enter, it should popup a very wordy dialog that shows us what
> arguments are being passed to the error page, and would be helpful information
> to have.
> 


Thanks.  I have attached the screencaps of the resulting javascript.  top image is when using IP address to access and the second image is using FQDN.

Comment 6

[Peter Santiago]

Attachment: javascript result

Comment 7

[Peter Santiago]

(In reply to comment #4)
> Sorry for the spam: I found the case again:
> http://www.geckozone.org/forum/viewtopic.php?t=66582 (there are some screen
> copies in it)
> 
> The cause of the invalidity of the cert was different (not issued for the right
> site), but the symptom (some <a in the message) was the same.
> 
> Safe-mode didn't cure the problem, but a new profile yes.
> 

I created a new profile as teoli suggested.  It worked.  This Firefox 3 installation was an upgrade from Firefox 2.  I'll try to check if this is coincidence or not.  I still have one Firefox 2 left to upgrade.  We'll see if the problem recurs after upgrade.  I'll keep you posted.

Comment 8

[Peter Santiago]

(In reply to comment #7)
> (In reply to comment #4)
> > Sorry for the spam: I found the case again:
> > http://www.geckozone.org/forum/viewtopic.php?t=66582 (there are some screen
> > copies in it)
> > 
> > The cause of the invalidity of the cert was different (not issued for the right
> > site), but the symptom (some <a in the message) was the same.
> > 
> > Safe-mode didn't cure the problem, but a new profile yes.
> > 
> 
> I created a new profile as teoli suggested.  It worked.  This Firefox 3
> installation was an upgrade from Firefox 2.  I'll try to check if this is
> coincidence or not.  I still have one Firefox 2 left to upgrade.  We'll see if
> the problem recurs after upgrade.  I'll keep you posted.
> 

Just upgraded from FF2 to FF3 on my other machine...  Didn't encounter the bug.
Worse of all, I deleted my old default profile so I can't retest it...  Sorry about that.  We can close the bug if that's ok with you guys

Comment 9

[Johnathan Nightingale [:johnath]]

(In reply to comment #8)

> 
> Just upgraded from FF2 to FF3 on my other machine...  Didn't encounter the bug.
> Worse of all, I deleted my old default profile so I can't retest it...  Sorry
> about that.  We can close the bug if that's ok with you guys
> 

Thank you for reporting it, and for your help trying to track it down.  It's not immediately clear to me why a new profile should have changed things, but given that there seems to be something non-standard at work, and given that you're happy to close it, so am I.