Different Keystore Password (was: XMPP Authentication issue with JDKKeyStore integrity)

[GoogleCodeExporter]

What steps will reproduce the problem?
0. Installing the application. Clean install
1. Start/Stop -> Setting up with XMPP + different login XMPP w/ server options
2. Start/Stop -> Wait for Connection

(Tried GTalk and different JIDs as well)

What is the expected output?
Seeing GTalkSMS connecting

What do you see instead?
"GTalkSMS: Wrong username or password"
and
W/System.err( 7975): java.io.IOException: KeyStore integrity check failed.
W/System.err( 7975):    at 
org.bouncycastle.jce.provider.JDKKeyStore.engineLoad(JDKKeyStore.java:888)
W/System.err( 7975):    at java.security.KeyStore.load(KeyStore.java:676)
W/System.err( 7975):    at 
org.jivesoftware.smack.ServerTrustManager.<init>(ServerTrustManager.java:63)
W/System.err( 7975):    at 
org.jivesoftware.smack.XMPPConnection.proceedTLSReceived(XMPPConnection.java:839
)
W/System.err( 7975):    at 
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:268)
W/System.err( 7975):    at 
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:44)
W/System.err( 7975):    at 
org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:71)

Additional informations:
GTalkSMS version = v2.1.2
Android OS version = 2.2.1
Phone model = HTC Vision (Desire Z)

Original issue reported on code.google.com by lhw.ri...@googlemail.com on 7 Apr 2011 at 1:55

Attachments:

• gtalksms.log

[GoogleCodeExporter]

The IOException came out of bouncycastle. Especially since it's an IO Exception 
I would guess that it is not an permanent error. Did you try to reinstall 
GTalkSMS? Did you enable debug log before gathering the log file?

Original comment by fschm...@gmail.com on 9 Apr 2011 at 10:03

[GoogleCodeExporter]

Of course I tried reinstalling it a few times. I also made sure there was no 
remaining data. I attached a more thorough log. From install and configuration 
to startup. I just cleaned out some unnecessary stuff like GSM and 
TextFieldChange events.

Original comment by lhw.ri...@googlemail.com on 9 Apr 2011 at 11:02

Attachments:

• log

[GoogleCodeExporter]

Did you cross check that the error exists with another XMPP Server? Looks like 
a SASL error.

Original comment by fschm...@gmail.com on 9 Apr 2011 at 3:20

[GoogleCodeExporter]

I tried my own Jabber server, GTalk and jabber.org
I attached the log for jabber.org but its just the same error with the 
keystore. I think I will just debug it.

Original comment by lhw.ri...@googlemail.com on 9 Apr 2011 at 3:33

Attachments:

• log

[GoogleCodeExporter]

I was able to track down the error. It seems like my keystore was widely 
different from the original one shipped by google. I'm currently running a 
slightly modified HTC rom but the keystore should be the same for all of them:
-rw-r--r--  1 root lhw  64K 2011-04-09 18:31 htc.bks
-rw-r--r--  1 root lhw 140K 2011-04-09 18:30 android3.bks
Which as it seems is not correct. The error was caused by a different storepass 
but when I replaced the on-device keystore no application reported keystore 
failures so I assume it should work now.

Original comment by lhw.ri...@googlemail.com on 9 Apr 2011 at 4:41

[GoogleCodeExporter]

try to set connection encryption to disabled in connection advance settings

Original comment by Florent....@gmail.com on 9 Apr 2011 at 8:58

[GoogleCodeExporter]

Is it one of the known ROMs? Do you now the other password? You should inform 
the dev's of the ROM that changing the password will probably break some apps.

Original comment by fschm...@gmail.com on 11 Apr 2011 at 5:00

[GoogleCodeExporter]

I also considered the possibility of them changing the password. But in turn 
they would've had change all the other Apps as well and as I wrote before 
everything works with the replaced keystore. But I will inform them of the 
possibly corrupt keystore.

Original comment by lhw.ri...@googlemail.com on 11 Apr 2011 at 5:02

[GoogleCodeExporter]

What ROM is it then? Nearly every app on Market (that uses the systems 
keystore) should have "changeit" hardcoded as password for the keystore, I just 
don't see a reason why any ROM developer would want to have another password.

Original comment by fschm...@gmail.com on 11 Apr 2011 at 5:28

[GoogleCodeExporter]

It's a slightly modified HTC Sense stock rom
http://forum.xda-developers.com/showthread.php?t=960149 from the virtuousrom 
guys. With their original virtuous ROM I ran into some issues so I switched to 
this one.
But as shown above the actual keystore is only 1/2 as big as the one supplied 
by Google so I just assume his is defect.

Original comment by lhw.ri...@googlemail.com on 11 Apr 2011 at 5:55

[GoogleCodeExporter]

Until we don't have more reports on this topic, we won't address this issue. It 
would be hard to deal with it anyways, as the Keystore password could be 
anything.

Original comment by fschm...@gmail.com on 13 Apr 2011 at 9:32

• Changed title: Different Keystore Password (was: XMPP Authentication issue with JDKKeyStore integrity)
• Changed state: WontFix