Closed Bug 586213 Opened 10 years ago Closed 10 years ago

Update app update url and certificate preferences after the additional host name with a new certificate is added for aus

Categories

(Firefox :: Preferences, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 4.0b7
Tracking Status
blocking2.0 --- betaN+

People

(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)

References

Details

Attachments

(2 files, 1 obsolete file)

New certificates (one active and one standby) for aus will be acquired in Bug 583678 and the new certificates will be for a new host name (possibly aus3.mozilla.org). After the new host name is added with the certificate the app.update.url preference will need to be changed to the new host name and the existing app.update.certs.* preference will need to be modified and the standby cert added. The cert preferences were added in bug 544442.
Nick, just a heads up.
cc'ing Daniel to give him a heads up as well
Why is a hostname needed for this?
*new hostname, that is.
By adding a new hostname with the new certs the change can be implemented immediately without having to add the existing cert to the prefs and waiting for the beta 3 or nightly users to upgrade to the next beta or nightly since aus2 will still be available with the previous cert.
Why not just get two new certs for aus2.m.o? The current cert is just the normal wildcard cert, no? Just not seeing why the change in hostname is needed, especially since we currently don't do any cert checking on AUS, afaik...
We do cert attribute checking on the client side - see bug 544442 - so, we wouldn't be able to deploy the new cert until after everyone has upgraded.
(In reply to comment #7)
> We do cert attribute checking on the client side - see bug 544442 - so, we
> wouldn't be able to deploy the new cert until after everyone has upgraded.

Ah! I didn't know that had landed yet. Ok, this makes more sense now. :)
Geotrust:

Your Web Server Certificate for aus3.mozilla.org

-----BEGIN CERTIFICATE-----
MIID1zCCA0CgAwIBAgIDFDu0MA0GCSqGSIb3DQEBBQUAME4xCzAJBgNVBAYTAlVT
MRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4IFNlY3VyZSBDZXJ0
aWZpY2F0ZSBBdXRob3JpdHkwHhcNMTAwODEwMDcwNzE4WhcNMTEwODEzMDE1NTM0
WjCBwDEpMCcGA1UEBRMgYWRWYUxrT2F3U01UT1RGV0pOVmpJbGhxc0FWRkl2dmYx
CzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1Nb3Vu
dGFpbiBWaWV3MRwwGgYDVQQKExNNb3ppbGxhIENvcnBvcmF0aW9uMSAwHgYDVQQL
ExdBdXRvbWF0aWMgVXBkYXRlIFN5c3RlbTEZMBcGA1UEAxMQYXVzMy5tb3ppbGxh
Lm9yZzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOxCTrFvoYr4j1z2
vhZRmAvAEABGOfgyfdjNQHxmwZOba4zYcTBaSFvKpbE7Cx1q1owRQOVsfbmnfjvB
lri1L4c3j+oavDchppk+qAXPOczHEq7v4FaNx/k22UrFmkw4tM8kEmOpwci4hW2m
wdNs6kAgQ2YNuleTBLjiFXc1eSCdbN/LQv7q3Xb+6lx6qLznO43o8Wnxsy6jca8t
P0FH+OSK7VGxbJQKVcT7fZWQWzt0mBMxaRAvmVuT45w3kZnqvMMUY9Ex/WK9o9HB
Ich80+cKrTNtvFreceHXPVM2UKtjuq41sNqvZcbjEmLyi0zOC5Znufx1KMl8LhVd
wYBf4ecCAwEAAaOByzCByDAfBgNVHSMEGDAWgBRI5mj5K9KylddH2CMgEE8zmJCf
1DAOBgNVHQ8BAf8EBAMCBPAwHQYDVR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMC
MBsGA1UdEQQUMBKCEGF1czMubW96aWxsYS5vcmcwOgYDVR0fBDMwMTAvoC2gK4Yp
aHR0cDovL2NybC5nZW90cnVzdC5jb20vY3Jscy9zZWN1cmVjYS5jcmwwHQYDVR0O
BBYEFHw/sCdL7A2CwaObV7FPUiqmb9XSMA0GCSqGSIb3DQEBBQUAA4GBAK/EvZeC
Dzpc+iB8zApukbbfabslyP2iX56ffJxdMB9kdqK5rNNT0pV/1QheHUYzh60EiUtN
IhwazcltGiYU4Fl3Gta8Rs18qmXIxqclsw4T4oefTp08WwNuqzAajhc0OElpdG4A
11v119yGQCpJxy1SsaK/9Ui/mRixd7HAZDmy
-----END CERTIFICATE-----
thawte's claiming a 2 day turn around.
Attached patch patch rev1 (obsolete) — Splinter Review
Requesting blocking.
blocking2.0: --- → ?
Attached patch patch rev2Splinter Review
Attachment #471595 - Attachment is obsolete: true
Attachment #474152 - Flags: review?(dtownsend)
Attachment #474152 - Flags: review?(dtownsend) → review+
blocking2.0: ? → betaN+
http://hg.mozilla.org/mozilla-central/rev/684e32fafe14
Status: NEW → RESOLVED
Closed: 10 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b6
You need to log in before you can comment on or make changes to this bug.