Closed
Bug 1095750
Opened 10 years ago
Closed 10 years ago
Make Docker use TLS_v1 protocol for TLSConfig
Categories
(MozReview Graveyard :: General, defect)
MozReview Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mconley, Assigned: mconley)
Details
Attachments
(1 file, 1 obsolete file)
I was hitting an error when trying to hack on MozReview, looking like this: requests.exceptions.SSLError: [Errno 1] _ssl.c:504: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version A quick search got me here: https://github.com/docker/docker-py/issues/364 Which suggests setting the ssl_version to TLS_v1 for the handshake. Doing that locally got rid of the problem for me, and I was successfully able to create a test instance of the MozReview infrastructure after that.
Comment 1•10 years ago
|
||
We should use TLS over SSLv23 anyway since it is the newer protocol. As long as clients and server support TLS, this should be a no-brainer.
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8519228 -
Flags: review?(gps)
Assignee | ||
Comment 3•10 years ago
|
||
/r/227 - Bug 1095750 - vcttesting: Make Docker use TLS_v1 protocol for TLSConfig. r=? Pull down this commit: hg pull review -r e96db8d4d1fd8b3c36077ae7347b5ff81997e4fe
Updated•10 years ago
|
Attachment #8519228 -
Flags: review?(gps) → review+
Comment 4•10 years ago
|
||
https://reviewboard.mozilla.org/r/225/#review113 Ship It!
Assignee | ||
Comment 5•10 years ago
|
||
https://hg.mozilla.org/hgcustom/version-control-tools/rev/dbdcef8198e9
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•9 years ago
|
||
Attachment #8519228 -
Attachment is obsolete: true
Attachment #8618580 -
Flags: review+
Assignee | ||
Comment 7•9 years ago
|
||
Updated•8 years ago
|
Product: Developer Services → MozReview
You need to log in
before you can comment on or make changes to this bug.
Description
•