MeinBMW Connector

[GoogleCodeExporter]

What steps will reproduce the problem?
1. try to send SMS
2. error: "MeinBMW: Not trusted server certificate"
3.

What is the expected output? What do you see instead?
"MeinBMW: Not trusted server certificate"

What version of the product are you using? On what operating system?
Vodafone HTC Magic, Android 2.2.1, WebSMS Version 3.2, MeinBMW Connector 
Version 1.2

Please provide any additional information below.
I just updated WebSMS to the latest version and now the error "FEHLER" occurs 
:-(

Can you help me?

Best regards!
Andy.

Original issue reported on code.google.com by Andy.Mi...@googlemail.com on 28 Oct 2011 at 6:56

[GoogleCodeExporter]

Original comment by f...@ub0r.de on 28 Oct 2011 at 7:40

• Added labels: Priority-High, Product-MeinBMW
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I'll have a look at this.

Original comment by silas.gr...@gmail.com on 29 Oct 2011 at 8:04

• Changed state: Accepted

[GoogleCodeExporter]

Hi!
Do you speak German?
I just installed again WebSMS 3.3 and now the "MeinBMW: Not trusted server 
certificate"
appears again instead of only "FEHLER".
Best regards

Original comment by Andy.Mi...@googlemail.com on 29 Oct 2011 at 8:09

[GoogleCodeExporter]

Yes, I'm German. I get the same error. Unfortunately I'm not an Android Dev in 
real life so I have to setup my development environment first. But I don't know 
how fast I'll be able to do that, sorry.

Maybe Felix changed something on the Connector base class or other parts of 
WebSMS API, so every connector has staten that he accepts untrusted SSL certs.

Felix?

Original comment by silas.gr...@gmail.com on 29 Oct 2011 at 8:31

[GoogleCodeExporter]

Ok, I think I know what's going on.

They exchanged the SSL cert, probably the old one was experired, so the 
Connector must be told to accept the new certificate.

Felix could you please do that? As mentioned before, I don't know when I'll 
find the time to set up an Android dev environment and all you have to do is to 
change line 60 in 
src/info/graffy/android/websms/connector/meinbmw/ConnectorMeinBMW.java

private final static String[] SSL_FINGERPRINTS = { 
"b4:2b:76:39:ec:53:ee:83:39:02:a3:70:c1:fc:a9:a5:f7:24:d5:2a" };

to the new cert from https://www.meinbmw.de

If not, I will be hopefully able to fix it in the next few days...

Silas

Original comment by silas.gr...@gmail.com on 29 Oct 2011 at 8:43

• Changed state: Started

[GoogleCodeExporter]

Hast Du auch eine Ahnung, warum ich MeinBMW 1.2.2 nicht installieren kann?
Beim Updaten erscheint "Die Paketdatei war nicht richtig signiert"...
Gruss, Andy. 

Original comment by Andy.Mi...@googlemail.com on 29 Oct 2011 at 9:58

[GoogleCodeExporter]

Sorry, no idea. Since I don't have a Market account, Felix publishes the 
connector for me :(

Original comment by silas.gr...@gmail.com on 29 Oct 2011 at 10:35

[GoogleCodeExporter]

pleaseconfirm this fix

http://websmsdroid.googlecode.com/files/Connector-MeinBMW-1.2.3.apk

Original comment by f...@ub0r.de on 29 Oct 2011 at 12:42

• Changed state: ShouldBeFixed

[GoogleCodeExporter]

Kann leider nicht installiert werden (wie schon MeinBMW 1.2.2.).
Bei der Installation kommt "Anwendung nicht installiert".
Bei MeinBMW 1.2.2 aus den Market kommt "Die Paketdatei war nicht richtig 
signiert".

Original comment by Andy.Mi...@googlemail.com on 29 Oct 2011 at 12:51

[GoogleCodeExporter]

Habe MeinBMW 1.2 deinstalliert und MeinBMW 1.2.3 istalliert. Jetzt scheint' 
wieder zu gehen.
Vielen Dank!

Original comment by Andy.Mi...@googlemail.com on 29 Oct 2011 at 1:24

[GoogleCodeExporter]

Original comment by f...@ub0r.de on 29 Oct 2011 at 3:05

• Changed state: Fixed