search

chunlinyao / m-im

Automatically exported from code.google.com/p/m-im
0 stars 0 forks source link

Nokia 6230i connecting to google gets SSL Error when SSL disabled #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install m-im (v1.3.1 in this case) on Nokia 6230i
2. Add new google account, leaving port on 5222 and SSL off
3. Connect, you will get a Null Pointer Exception

What is the expected output? What do you see instead?

Expected output is a successful connection and loading of the buddy list.
The NPE causes the application to close. If I do the same in the 6230i
emulator, I get a certificate exception before the NPE.

Output from the emulator using a non-obfuscated (DEBUG) build is as follows

----
Method : GET
loading
url=https://www.google.com:443/accounts/ClientAuth?Email=username@gmail.com&Pass
wd=secret&PersistentCookie=false&source=mgtalk
Exception: javax/microedition/pki/CertificateException
        at com.sun.midp.io.j2me.http.Protocol.checkForException(+51)
        at com.sun.midp.io.j2me.http.Protocol.readResponseMessage_wap(+28)
        at com.sun.midp.io.j2me.http.Protocol.connect_wap(+402)
        at com.sun.midp.io.j2me.http.Protocol.connect(+27)
        at com.sun.midp.io.j2me.http.Protocol.openInputStream(+64)
        at com.sun.midp.io.j2me.http.Protocol.openDataInputStream(+28)
        at net.sourceforge.jxa.Jxa.generateTokenViaGoogle(+82)
        at net.sourceforge.jxa.Jxa.login(+170)
        at net.sourceforge.jxa.Jxa.run(+40)
Exception: javax/microedition/pki/CertificateException
        at com.sun.midp.io.j2me.http.Protocol.checkForException(+51)
        at com.sun.midp.io.j2me.http.Protocol.readResponseMessage_wap(+28)
        at com.sun.midp.io.j2me.http.Protocol.connect_wap(+402)
        at com.sun.midp.io.j2me.http.Protocol.connect(+27)
        at com.sun.midp.io.j2me.http.Protocol.openInputStream(+64)
        at com.sun.midp.io.j2me.http.Protocol.openDataInputStream(+28)
        at net.sourceforge.jxa.Jxa.generateTokenViaGoogle(+82)
        at net.sourceforge.jxa.Jxa.login(+170)
        at net.sourceforge.jxa.Jxa.run(+40)
        at com.sun.midp.io.j2me.http.Protocol.checkForException(+51)
        at com.sun.midp.io.j2me.http.Protocol.readResponseMessage_wap(+28)
        at com.sun.midp.io.j2me.http.Protocol.connect_wap(+402)
        at com.sun.midp.io.j2me.http.Protocol.connect(+27)
        at com.sun.midp.io.j2me.http.Protocol.openInputStream(+64)
        at com.sun.midp.io.j2me.http.Protocol.openDataInputStream(+28)
        at net.sourceforge.jxa.Jxa.generateTokenViaGoogle(+82)
        at net.sourceforge.jxa.Jxa.login(+170)
        at net.sourceforge.jxa.Jxa.run(+40)
javax.microedition.pki.CertificateException: Certificate failed verification
----

This might not be fixable unless we can find a way to update the
certificate store within m-im or on the phone natively, but not sure this
is possible.

Mark

Original issue reported on code.google.com by markmcna...@gmail.com on 5 Jul 2009 at 11:42

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
We can't fix the Certificate failed,But we can close the connection normally 
without NPE.

Original comment by chunlinyao@gmail.com on 7 Jul 2009 at 2:46