Closed
Bug 883915
Opened 12 years ago
Closed 12 years ago
"Protocol SSL_RSA_WITH_RC4_128_SHA is not supported" on Android 2.2 devices
Categories
(Firefox Health Report Graveyard :: Client: Android, defect, P1)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: nalexander, Assigned: nalexander)
References
Details
From twalker, on a 2.2 HTC device:
06-17 11:36:53.607: D/GeckoPreferences(658): Broadcast: org.mozilla.fennec.HEALTHREPORT_UPLOAD_PREF, android.not_a_preference.healthreport.uploadEnabled, GeckoApp, true
06-17 11:36:53.627: D/GeckoSetPrefs(658): Broadcast pref.
06-17 11:36:53.657: I/GeckoHealth(658): fennec :: HealthReportBroadcastService :: Registering health report start broadcast receiver.
06-17 11:36:53.657: I/GeckoHealth(658): fennec :: BackgroundService :: Setting inexact repeating alarm for interval 60000
06-17 11:36:53.718: I/GeckoHealth(658): fennec :: SubmissionPolicy :: Need to wait 120000 before first upload.
06-17 11:38:53.717: I/GeckoHealth(658): fennec :: GeckoHealthGen :: Generating FHR document from 1355935133716; last ping 1367500000000
06-17 11:38:53.717: I/GeckoHealth(658): fennec :: GeckoProfileInfo :: Restoring ProfileInformationCache from file.
06-17 11:38:59.047: W/GeckoHealth(658): fennec :: TLSSocketFactory :: Setting enabled cipher suites failed: Protocol SSL_RSA_WITH_RC4_128_SHA is not supported.
This looks a lot like https://bugzilla.mozilla.org/show_bug.cgi?id=717691.
Comment 1•12 years ago
|
||
I do not see this on Android 3.1 on a Samsung Galaxy 10 tablet.
Comment 2•12 years ago
|
||
Tracy: did I see you mention on IRC that you couldn't reproduce this?
Assignee | ||
Comment 3•12 years ago
|
||
I should have updated: this message is printed by the BaseResource code catching a known exception and fixing it up. Not sure what causes the later failure; presumably the cert issue in Bug 828654 itself.
Comment 4•12 years ago
|
||
So I guess that's INVALID!
See Bug 884008 for the cert issue.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Comment 5•12 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=828654#c32 and https://bugzilla.mozilla.org/attachment.cgi?id=763685 for what I saw after going back to test the 2.2 device.
Updated•7 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•