Closed Bug 658812 Opened 13 years ago Closed 13 years ago

Untrusted Connection Warning (Although I have Certificate)

Categories

(Core :: Security: PSM, defect)

x86
Windows 7
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: efegencer, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

In previous versions of Firefox, I did not have this problem but after updating to version 4 of Firefox, I encountered this problem several times (but weirdly not always). When I try to login my school registration system, I get "This Connection is Untrusted" error and (although I have already installed the certificate before) when I try to click "Add Exception" button I see that I already have the certificate installed (which is correct):

Certificate Status:
Valid Certificate
...

but I cannot pass the "This Connection is Untrusted" page in any way. I have no problem in using the system via Chrome or IE or Safari but in Firefox, I get this error. Let me repeat that this error first started to occur after updating Firefox to version 4. My current version is 4.0.1

Thanks,
Efe


Reproducible: Sometimes

Steps to Reproduce:
1. visit https://registration.boun.edu.tr/
2. click Student Information
3. Cannot go further even though I already have the certificate installed


Expected Results:  
No "This Connection is Untrusted" screen...
Version: unspecified → 4.0 Branch
Please provide the technical details of the connection error
The website is using its own root certificate. Visit http://registration.boun.edu.tr/. There will be a link "SSL Certificate" that gives instructions for importing the certificate into the browser and trusting it. :(

I think the reporter is saying that the certificate had already been imported and was working fine in Firefox 3.x, but in Firefox 4 it doesn't work anymore.
(In reply to comment #2)
> The website is using its own root certificate. Visit
> http://registration.boun.edu.tr/. There will be a link "SSL Certificate"
> that gives instructions for importing the certificate into the browser and
> trusting it. :(
> 
> I think the reporter is saying that the certificate had already been
> imported and was working fine in Firefox 3.x, but in Firefox 4 it doesn't
> work anymore.

This is exactly what the problem is.
Thanks,
WFM on:
 Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110522 Firefox/6.0a1

*Note: In reply to Comment 3, the certificate may be lost after an update from 3.6
I could not verify the update. But once you add a security exception in your current Firefox build it remains saved (unless you delete your whole profile).
Remaining Unconfirmed.
I have taken 2 snapshots of the problem. Maybe they would be helpful:

Certificate details (it says, "could not verify this certificate for unknown reasons"):
http://imageshack.us/photo/my-images/641/certificateviewer.jpg/

Seems like I already have the valid certificate:
http://imageshack.us/photo/my-images/193/snapshotbb.jpg/

Thanks,
What happens if you create a new profile and test with this profile ?
- http://support.mozilla.com/en-US/kb/Managing-profiles
Is this the same problem as reported in bug 660749 ?
@Kai Engert: yes it seems that it is exactly the same problem with that bug. I updated Firefox to 5.0 but the problem is still there.
(In reply to comment #8)
> @Kai Engert: yes it seems that it is exactly the same problem with that bug.
> I updated Firefox to 5.0 but the problem is still there.

Since bug 660749 is already set on new this can be set as duplicate. Thanks for reporting the issue
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
The site now uses a certificate issued by GoDaddy so it will not be possible to verify that this issue is fixed after bug 660749 is fixed.
Component: Security → Security: PSM
Product: Firefox → Core
QA Contact: firefox → psm
Resolution: DUPLICATE → WORKSFORME
Version: 4.0 Branch → unspecified
You need to log in before you can comment on or make changes to this bug.