1140384 - JavaScript Error: "push.services.mozilla.com : server does not support RFC 5746, see CVE-2009-3555

Status: RESOLVED DUPLICATE of bug 1018878

(Cloud Services Graveyard :: Server: SimplePush, defect)

Description

[:hellosct1]

Attachment: logcat complete file

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150222232811

Steps to reproduce:

I am on the desk, I have no applications launched

I see the icon appear updated regularly and disappear

I have the following message (extract log)

E/HWComposer(  212): Non-uniform vsync interval: 9095157909
E/HWComposer(  212): Non-uniform vsync interval: 11457685
E/HWComposer(  212): Non-uniform vsync interval: 17759115
E/HWComposer(  212): Non-uniform vsync interval: 15624896
W/GeckoConsole(  212): [JavaScript Error: "push.services.mozilla.com : server does not support RFC 5746, see CVE-2009-3555"]
W/GeckoConsole(  212): [JavaScript Error: "push.services.mozilla.com : server does not support RFC 5746, see CVE-2009-3555"]
E/HWComposer(  212): Non-uniform vsync interval: 17378803
E/HWComposer(  212): Non-uniform vsync interval: 15974688




Actual results:

not normal consumption of the battery

Comment 1

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

QAWanted to reproduce on Flame.

Hi heelosc1, 
What's the device you're using to test?

Comment 2

[:hellosct1]

I have Flame

BootGecko 2.2.0.0-prerelease
qcom
eng.cltbld.20150217.040936
version : 37.0
login of version : 20150309162503
canal update : nightly-b2g37
Git : 2015-03-06 18:26:27 (166491b9)

thank's

Comment 3

[Pi Wei Cheng [:piwei] (inactive)]

Reporter, could you be more specific about

> I see the icon appear updated regularly and disappear

What icon? Can you provide a screenshot of the issue?

Comment 4

[:hellosct1]

hi

this capture is here : 
www.hello-design.fr/download/flame-2015-03-12-22-43-49.png

It is up to the capture and I circled in red the icon that appears regularly. When the icon appears, I get an error that appears in the logcat file

I can show it to :jlorenzo or :lissyx+mozillians
I am next to Mozilla Paris


Christophe

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

You will see that icon because that icon represents data being transferred.  
The data being transferred is basically letting you know the error in the log.

Just wondering, where did you get the phone/build?  I can't seem to reproduce.  Was there a setting you changed?

Comment 6

[:hellosct1]

hi,

Yes I know it is for the transfer of data, but each time it queries the server, there is a mistake and it's non-stop, he spends his time query the server that does not answer
The result, in two hours he discharged battery

The last update (Reset flame) was carried out with :Gerard-majax (:lissyx+mozillians) and since then I do everyday automatic updates

I can switch back to see :Gerard-majax (:lissyx+mozillians) or :jlorenzo at the Mozilla Paris . They know me well because they voyent regularly with the tickets that I post

thank's

Christophe

Comment 7

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Ah, I see.  I apologize, I didn't understand the situation.  I think I understand it a little better.
Did you use any service like Where's my Device?

I'm trying to figure out where the push notification started from.

NI? on Kit as he's probably more familiar with this part than I am.

Comment 8

[:hellosct1]

I think tomorrow (Friday), I'll go to give Mozilla Paris (:Gerard-majax and :jlorenzo) for to see where exactly is the problem
and when it triggers compared with logcat I already sent

Christophe

Comment 9

[Pi Wei Cheng [:piwei] (inactive)]

(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #1)
> QAWanted to reproduce on Flame.

Unable to reproduce this on Flame 2.2. I had cellular data enabled, sitting on Homescreen and I didn't get that error. It did display the said error when I enabled Find My Device in Settings, but the error only displayed once and it was not continuous.

Device: Flame 2.2 (full flash, 319MB)
BuildID: 20150312002501
Gaia: 572d60e0a440ee4af50bc6b6adad8876eadbdb4d
Gecko: 244e6ba3c20e
Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 10

[Lina Butler (ex-Mozilla)]

This looks like it's related to bug 970453...as :jrconlin noted, Go's TLS implementation does not support renegotiation, and will close the connection with an `internal_error` if the client attempts it: https://github.com/golang/go/blob/go1.4.2/src/crypto/tls/conn.go#L513-515

I suspect this false positive arises because Go doesn't support renegotiation at all, but RFC 5746 states: "In order to enable clients to probe, even servers that do not support renegotiation MUST implement the minimal version of the extension described in this document for initial handshakes, thus signaling that they have been upgraded."

Comment 12

[Lina Butler (ex-Mozilla)]

Oops, I meant to link this to bug 970453, not mark it as a dupe...my apologies.

Comment 13

[:gerard-majax]

Christophe, I think I already told you that I'm convinced your battery drain is not related to the error itself, but rather that you just have something going on with your device. The fact hat you keep getting timeouts on window manager stuff, for example ...

Comment 14

[Johan Lorenzo [:jlorenzo]]

(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #7)
> Did you use any service like Where's my Device?

Per the logs, Find my device shows some activity but the errors comes before FMD.

Comment 15

[Josh Cheng [:josh]]

Hi Thinker,
This seems to be push.server issue. Could you please have a look?
Thank you!

Comment 16

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Bobby, can you triage this?

Comment 17

[Bobby Chien]

Doug, could you help to answer Simple Push server issue?

Comment 18

[Bobby Chien]

I think this is duplication of bug 1018878.

Comment 19

[:hellosct1]

hi :josh

With various updates and to have everything completed for services
The message appears from time to time but it is reasonable