Closed Bug 408694 Opened 18 years ago Closed 18 years ago

Chat server needs to use a proper certificate

Categories

(support.mozilla.org Graveyard :: Chat, defect)

Product:
support.mozilla.org Graveyard
Component:
Chat
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: Kensie, Assigned: justin)

Details

On the testing server there's an unsigned cert for the ssl. This breaks on trunk/FF3. Adding an exception for the cert is difficult and seems prone to fail, besides that, we can't expect user to manually accept a cert to use us. The production server needs to just work.
Attached CSR or tell me what hostname this is going to be using and I'll do it.
We've (SUMO team) decided the chat server should be on chat.support.mozilla.com but I believe that needs to be set up yet, as well.
Who needs to access this? Internal folk or random Internet users? Put another way, will a Mozilla self-signed certificate work?
-----BEGIN CERTIFICATE REQUEST----- MIICWDCCAcECAQAwgb0xCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlh MRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRwwGgYDVQQKExNNb3ppbGxhIENvcnBv cmF0aW9uMRkwFwYDVQQLExBMaXZlIENoYXQgU2VydmVyMSEwHwYDVQQDExhjaGF0 LnN1cHBvcnQubW96aWxsYS5jb20xJTAjBgkqhkiG9w0BCQEWFmhvc3RtYXN0ZXJA bW96aWxsYS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALY9Q0hW44O/ bJ9lwnMTvYLqu6MhipIn8B9sAjmON333hn07iaCnRfhKbamuH5pW1iZl3YCsoa7T vJODljL4SyZaHrh0E1sg+tBPycsgBeMp26nc4OKTTJvTqrec3P+DYll/g81m1zg7 z0NeshoHsf5b7xUFQrJY28j3KPXQjkCpAgMBAAGgWjBYBgkqhkiG9w0BCQ4xSzBJ MBEGCWCGSAGG+EIBAQQEAwIGQDAMBgNVHRMBAf8EAjAAMCYGA1UdEQQfMB2CG3d3 dy50cnVuay5zdGFnZS5tb3ppbGxhLmNvbTANBgkqhkiG9w0BAQQFAAOBgQBPr571 7rJT7cZCvBKY6yso5iCtob7F+uBosllMIHRCYLOpqG3+xgsbUWPNkCFNWRKEAmtN yKpoWUKWsTsDPvvM0XDwerqxCTtbzOZ9CFGpYAb09YG648+Mc7g+oIupP+PE0vqd 1xunlmgrVD9WOJCQCvxEXx/7FCa7teRpdWLj6Q== -----END CERTIFICATE REQUEST-----
Who can answer mrz's question? We really need to get this up asap if we are to have a test day tomorrow.
One that time line the only thing I can certainly get you is a Mozilla-signed certificate. If you decide you need something else, let me know. I've coped the key and certificate to dm-chat01:/root/ .
The problem is that I personally have no idea what to do with it. :) morgamic?
Needs to be public, the 9091 port is also used for the public client.
ports already open. Are you asking GIF a non-mozilla signed cert?
So the self signed cert will work for testing, but we'll want a proper cert to go live. (yay trunk!) When can that be done for us? I can work around it until then.
I botched the CSR - re-attaching and passing off for cert ... -----BEGIN CERTIFICATE REQUEST----- MIICMDCCAZkCAQAwgb0xCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlh MRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRwwGgYDVQQKExNNb3ppbGxhIENvcnBv cmF0aW9uMRkwFwYDVQQLExBMaXZlIENoYXQgU2VydmVyMSEwHwYDVQQDExhjaGF0 LnN1cHBvcnQubW96aWxsYS5jb20xJTAjBgkqhkiG9w0BCQEWFmhvc3RtYXN0ZXJA bW96aWxsYS5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALY3IvdVi5Xv e05Zr7I5Uwq1HpVU9X1ljCIDdnSgOkDS+sPeR34LQVBBjsuhVPSxyD4NwKaaKjpq g5AeYUvqk7EgvB+c47386+Np/xSNGQegHWSo5yNyhjgR7ji1HDE8SGXHUC0lT4Fc Z7VfRVjEiniAMFOVgKWLVYf4S79N0scfAgMBAAGgMjAwBgkqhkiG9w0BCQ4xIzAh MBEGCWCGSAGG+EIBAQQEAwIGQDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA A4GBALI6LQUb6nNDGJCWAfv/PGP/A3lC22xw5XYx/41eq5+2HX3zsSFxagLN2CAG +N+7oQepJ0fHZY2o0EfXA2IcjSMfKFGl11Eqj4a1DynxeyfVoVbX6wGm6lZr55Yt AgxcmWtaD63OOpe4WvannB5sW3Lbc6IH++jO/no5tiqTUGau -----END CERTIFICATE REQUEST-----
Assignee: nobody → justin
see also Bug 409431
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Verified
Status: RESOLVED → VERIFIED
Product: support.mozilla.org → support.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.