Bug #4589
closed
[API] Problem connecting using Firefox
Added by Peter Amstutz about 10 years ago.
Updated about 10 years ago.
Estimated time:
(Total: 0.00 h)
Description
Firefox 31+ increased SSL certificate checking in a way that seems to silently break on our self-signed development/test certificates. (I thought this was due to MD5 but on further investigation the certs are using either SHA1 or SHA256.)
Figure out what is causing this and adjust certificate generation to fix it.
^^^ This is wrong.
- Description updated (diff)
- Subject changed from [API] SSL certs used for development/testing should be signed with SHA1 instead of MD5 to [API] SSL certs used for development/testing should be signed with SHA2 instead of MD5
- Target version changed from Bug Triage to 2014-12-10 sprint
- Assigned To set to Peter Amstutz
- Subject changed from [API] SSL certs used for development/testing should be signed with SHA2 instead of MD5 to [API] SSL certs used for development/testing are invalid when used with Firefox
- Description updated (diff)
As far as I can tell, the problem is simply that Firefox has gotten in its head that connections to localhost:3001 should go into a black hole. Here's the workaround:
cd ~/.mozilla/firefox/xxxxx.default
mv cert8.db cert8.db.old
- Subject changed from [API] SSL certs used for development/testing are invalid when used with Firefox to [API] Problem connecting using Firefox
- Description updated (diff)
Since we have a workaround I'm going to mark this as resolved.
- Status changed from New to Resolved
Also available in: Atom
PDF
Updated by 
Updated by