Closed
Bug 722561
Opened 13 years ago
Closed 13 years ago
TLSSocketFactory.java always returns that a socket is secure
Categories
(Firefox for Android Graveyard :: Android Sync, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla13
People
(Reporter: dchanm+bugzilla, Assigned: nalexander)
References
Details
(Whiteboard: [qa-])
Although the spec defines that TLS/SSL sockets are always secure [1], we may want to perform additional checks based on whether setEnabledCipherSuites() failed or not. [2]
[1] - http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/conn/ssl/SSLSocketFactory.html#isSecure%28java.net.Socket%29
[2] - https://github.com/mozilla-services/android-sync/blob/develop/src/main/java/org/mozilla/gecko/sync/net/TLSSocketFactory.java#L103
Updated•13 years ago
|
Priority: -- → P3
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → nalexander
Comment 1•13 years ago
|
||
Comment 2•13 years ago
|
||
wrt the original direction of the bug: I'm pretty happy just allowing the default implementation to decide whether the negotiated connection was secure.
If setting the cipher suites failed, we'll just use a less-preferred one (which is probably the one we prefer, just under a different name). At no point will we negotiate a non-secure connection.
Comment 3•13 years ago
|
||
Target Milestone: --- → mozilla13
Updated•13 years ago
|
Whiteboard: [qa-]
Updated•12 years ago
|
Product: Mozilla Services → Android Background Services
Updated•7 years ago
|
Product: Android Background Services → Firefox for Android
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•