Closed Bug 1036130 Opened 11 years ago Closed 11 years ago

Provide secure Bugzfeed endpoint

Categories

(bugzilla.mozilla.org :: Infrastructure, defect)

Production
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: kohei, Assigned: glob)

Details

I have added a Bugzfeed support to my BzDeck app but noticed that it didn't work on production. It's due to a SecurityError "The operation is insecure" because https://www.bzdeck.com/ is secure but ws://bugzfeed.mozilla.org/ is not. Looks like it's a common WebSocket issue. Could you provide a secure endpoint? Thanks!
Component: Bugzilla Change Notification System → Infrastructure
QA Contact: mcote
Summary: Bugzfeed cannot be used by secure sites due to a SecurityError → Provide secure Bugzfeed endpoint
Yes, good point, there should be a secure endpoint. We'll have to get a cert for it, so it'll take a couple days.
Assignee: nobody → glob
the version of haproxy installed/available doesn't support ssl (1.4). we require version 1.5 of haproxy, but that was only released a month ago. as i'd prefer not to build from source, a lightweight workaround is to use stunnel to terminate ssl connections and tunnel them to the bugzfeed server. i've tested this with a self-signed certificate and it works. i've filed bug 1038581 to get a real certificate issued.
Any updates? This is blocking our Alpha 10 release. https://github.com/kyoshino/bzdeck/issues?milestone=15
Friendly ping
not forgotten :) i'm waiting on an updated certificate from gozer.
Bug 1038581 says the cert has already been sent...?
(In reply to Kohei Yoshino [:kohei] from comment #6) > Bug 1038581 says the cert has already been sent...? unfortunately i wasn't able to decrypt it, totally due to my own fault (bad pgp key). i immediately provided gozer with an alternative key, and i've just pinged him a reminder.
deployed!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Awesome!
Deployed our BzDeck update. Thanks so much! https://www.facebook.com/BzDeck/posts/555860127873034
You need to log in before you can comment on or make changes to this bug.