Closed Bug 763159 Opened 12 years ago Closed 12 years ago

Test failure 'secure.mur.at == erle.mur.at ' in testSecurity/testUnknownIssuer.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)

defect

Tracking

(firefox21 fixed, firefox22 fixed, firefox23 fixed, firefox24 fixed, firefox-esr17 fixed)

RESOLVED FIXED
Tracking Status
firefox21 --- fixed
firefox22 --- fixed
firefox23 --- fixed
firefox24 --- fixed
firefox-esr17 --- fixed

People

(Reporter: whimboo, Assigned: daniela.p98911)

References

()

Details

(Whiteboard: [mozmill-test-failure] s=121210 u=failure c=security p=1)

Attachments

(4 files, 1 obsolete file)

This test is failing all the time now because mur.at has changed its certificate. Now it's not an unknown but untrusted one. We should disable this test for now immediately to not cause more failure messages and find out how we can come up with a test case on mozqa.com. I will push a band-aid fix right away which skips the test.
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][mozmill-test-skipped]
Remus, would you mind to disable the appropriate Litmus tests? I would appreciate that. Also could you check how we could create such an unknown issuer certificate? Not sure if this page helps but I think the web should be full of examples. http://stackoverflow.com/questions/275878/firefox-and-ssl-sec-error-unknown-issuer We should then get an infrastructure bug filed to get this implemented on mozqa.com.
Flags: in-litmus?(remus.pop)
Disabled Litmus tests ids: esr10: 41457 release (13): 5632 beta (14): 64706 aurora (15): 16359
Flags: in-litmus?(remus.pop) → in-litmus-
Visiting the website we use for testing redirects me to https://sicher.mur.at/ . Couldn't we use this instead?
No, this is not an unkown issuer certificate. We have to create our own example on mozqa.com.
Remus, do you have an update? Nearly two weeks have been passed by.
(In reply to Henrik Skupin (:whimboo) from comment #6) > Remus, do you have an update? Nearly two weeks have been passed by. Giving comment 5, we have to change the test page to one from mozqa.com right? If so, adding bug 661121 to depencies
Depends on: 661121
Not yet, as long as we do not have a valid cert for this test. I don't want to block the work on bug 661121 for that.
No longer depends on: 661121
In order to be able to connect to a server through ssl, a list of certificates must be presented. There are some intermediate certificates which if they aren't installed, Firefox will complain about this unknown issuer. So basically we only need to install the root certificate leaving the intermediates (they should be supplied with the root, but as separate files) out. This should give insight about how they look like: https://support.comodo.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1182
Priority: -- → P2
Assignee: hskupin → nobody
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] → [mozmill-test-failure][mozmill-test-skipped] s=121112 u=failure c=security p=1
Assignee: nobody → alex.lakatos
We got a more important failure today we have to take care of. Lets drop this bug from this weeks sprint and do bug 810820 instead.
Assignee: alex.lakatos → nobody
Status: ASSIGNED → NEW
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] s=121112 u=failure c=security p=1 → [mozmill-test-failure][mozmill-test-skipped]
Lets follow up on Remus investigation and find a fix in the next two weeks so that we can get this test re-enabled.
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] → [mozmill-test-failure][mozmill-test-skipped] s=121210 u=failure c=security p=1
Assignee: nobody → andreea.matei
When are you going to proceed on this bug?
Status: NEW → ASSIGNED
Assignee: andreea.matei → dpetrovici
I will work on this bug. I have looked at Remus' investigation and ran the test. It appears we need a page on mozqa.com where we can have a self signed SSL certificate with no issuer (added for CA) so that we can get the "sec_error_unknown_issuer" error. But just to make sure I will discuss with our IT and try to create such an SSL certificate locally and see if the test can be fixed by this.
Based on discussion with Dave in Ask an expert meeting, I will log a bug for Mozilla IT to create a certificate and add it to mozqa.com site. This will help to re-enable and update the test. I have logged bug 828981
Depends on: 828981
Lets get this test updated and re-enabled now that we have such a broken SSL cert in-house.
Comment on attachment 747378 [details] [diff] [review] patch v1.0 Review of attachment 747378 [details] [diff] [review]: ----------------------------------------------------------------- ::: tests/functional/testSecurity/testUnknownIssuer.js @@ +21,5 @@ > controller.waitForPageLoad(); > > var link = new elementslib.ID(controller.tabs.activeTab, "cert_domain_link"); > controller.waitForElement(link); > + expect.equal(link.getNode().textContent, "ssl-selfsigned-unknownissuer.mozqa.com", "Domain name is visible"); I think this line exceeds 80 chars.
Attachment #747378 - Flags: review?(andreea.matei) → review-
Attached patch patch v1.1Splinter Review
Modified patch based on review
Attachment #747378 - Attachment is obsolete: true
Attachment #747402 - Flags: review?(andreea.matei)
Comment on attachment 747402 [details] [diff] [review] patch v1.1 Review of attachment 747402 [details] [diff] [review]: ----------------------------------------------------------------- ::: tests/functional/testSecurity/testUnknownIssuer.js @@ +9,3 @@ > > +var setupModule = function(aModule) { > + aModule.controller = mozmill.getBrowserController(); We should really only modify lines which are important to get the bug fixed. Please avoid those side-by changes in the future. It's not a blocker to get this patch landed through.
Comment on attachment 747402 [details] [diff] [review] patch v1.1 Review of attachment 747402 [details] [diff] [review]: ----------------------------------------------------------------- Landed as: http://hg.mozilla.org/qa/mozmill-tests/rev/7de23ec0585d (default)
Attachment #747402 - Flags: review?(andreea.matei) → review+
The patch for default/Aurora does not apply cleanly on Beta branch due to changing of the TEST_DATA on default. This patch also does not apply cleanly on Release. Reports for Beta: - Linux: http://mozmill-crowd.blargon7.com/#/functional/report/14f8bc4e22e61353662cded4c235d1e1 - MAC: http://mozmill-crowd.blargon7.com/#/functional/report/14f8bc4e22e61353662cded4c2389341 - Windows: http://mozmill-crowd.blargon7.com/#/functional/report/14f8bc4e22e61353662cded4c2387b65
Attachment #749842 - Flags: review?(andreea.matei)
Attachment #749842 - Flags: review?(andreea.matei) → review+
Attachment #749885 - Flags: review?(andreea.matei) → review+
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [mozmill-test-failure][mozmill-test-skipped] s=121210 u=failure c=security p=1 → [mozmill-test-failure] s=121210 u=failure c=security p=1
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: