search

rschilling / websmsdroid

Automatically exported from code.google.com/p/websmsdroid
0 stars 0 forks source link

invalid SSL-certificate with O2-Connector #600

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Checking number of left free sms
2.sending a sms
3.

What is the expected output? What do you see instead?
It does not check the number of free SMS and it does not send sms. Instead  get 
the notification: "o2: Der Server konnte sich nicht ausweisen (ungültiges SSL 
Zertifikat). Bitte aktualisieren Sie diesen Connector. Versuchen Sie 
´ignoriereungültiges SSL Zertifikat´in den Einstellungen zu aktivieren falls 
das Problem weiter besteht."

What version of the product are you using? On what operating system?
WebSMS v4.1
WebSMS O2 Connector 1.7.2 (by Imb)
Android 2.3.3 with HTC Sense 2.1 (HTC Wildfire S)

Please provide any additional information below.
I activated "ignoriere ungültiges SSL-Zertifikat". But it did the same.
I deinstalled and reinstalled the connector, what did not help either.

Original issue reported on code.google.com by nbiec...@gmail.com on 25 Oct 2011 at 1:57

GoogleCodeExporter commented 9 years ago 
I had the same problem at SGS 2

Original comment by Jagdwuf...@gmail.com on 25 Oct 2011 at 4:54

GoogleCodeExporter commented 9 years ago 
Ok, for some unkown reason everything is working normal again. Hope it keeps 
working. Thanks anyway :)

Original comment by nbiec...@gmail.com on 25 Oct 2011 at 4:58

GoogleCodeExporter commented 9 years ago 
Issue 601 has been merged into this issue.

Original comment by f...@ub0r.de on 26 Oct 2011 at 5:28

GoogleCodeExporter commented 9 years ago 
not working. getting:
"the server did not properly identify itself (invalid SSL certificate). Please 
update this connector. If the problem persists, try turning on 'ignore invalid 
SSL certificates' in settings."
I tried the recommended step and it didn't do anything.

Original comment by beawe2...@googlemail.com on 26 Oct 2011 at 2:38

GoogleCodeExporter commented 9 years ago 
Issue 603 has been merged into this issue.

Original comment by f...@ub0r.de on 26 Oct 2011 at 3:51

GoogleCodeExporter commented 9 years ago 
Yep, problem is also back here. Without changing anything on my phone the 
problem seems to come and go ;)

Original comment by nbiec...@gmail.com on 26 Oct 2011 at 4:06

GoogleCodeExporter commented 9 years ago 
Issue 604 has been merged into this issue.

Original comment by f...@ub0r.de on 28 Oct 2011 at 6:43

GoogleCodeExporter commented 9 years ago 
today it's working again.
both sending sms and checking the remaining free sms.

Original comment by lOtz1...@gmail.com on 28 Oct 2011 at 7:01

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago 
Today it is working again, o2 seems to be making some changes on their 
backend!!!

Original comment by beawe2...@googlemail.com on 29 Oct 2011 at 8:17

GoogleCodeExporter commented 9 years ago 
Here 7th day of non-working. :-(

Original comment by rainer.s...@gmail.com on 31 Oct 2011 at 6:02

GoogleCodeExporter commented 9 years ago 
Hello Rainer,

I'm aware of the issue, unfortunately i can not replicate the bug. I need 
someone who is affected to grab the email.o2online.de / login.o2online.de SSL 
Fingerprints, i can then update the connector.

P.S.: Does enabling "ignore invalid ssl certificates" in o2 Settings clear the 
issue?

Original comment by sca...@gmail.com on 31 Oct 2011 at 1:11

GoogleCodeExporter commented 9 years ago 
The Ignore Setting doesn't work. I am affected. If you need anything just ask.

Original comment by phuber.m...@gmail.com on 31 Oct 2011 at 1:15

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
it works again. had the ssl error on 29/10, even w/ ignore ssl activated.
just sent a text w/ the option deactivated, it went through and arrived 
perfectly.

Original comment by m...@mitjaveil.com on 31 Oct 2011 at 1:19

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
We already had 3 people here stating that "ignore invalid ssl certificates" 
does NOT help during the last week. Two in this bug, me in #603 
http://code.google.com/p/websmsdroid/issues/detail?id=603

Today the o2-connector works here. I guess fetching fingerprints can only be 
done on days it doesn't work, is this correct? And does it need to be done via 
the phone?

Original comment by sogn...@gmail.com on 31 Oct 2011 at 1:22

GoogleCodeExporter commented 9 years ago 
Yeah, it seems that the setting is broken, my bad. I'll have to look into
it.
Yes, sending needs to be "broken" to get the required information. You
should be able to grab it with your computer, as long as you use the same
internet connection as your mobile phone (i.e. same WLAN).

In Chrome:

   1. Click the little lock icon to the left of the url
   2. Click "Zertifikateinformationen"
   3. Click on Tab "Details"
   4. Scroll down till you reach "Fingerabdruck" and copy & paste it
   5. Thanks!

Original comment by sca...@gmail.com on 31 Oct 2011 at 1:40

GoogleCodeExporter commented 9 years ago 
Fingerprint: b0 36 f6 fd 0b 6f 28 75 ca 3b 5d 4a 91 07 ce db d0 0d 71 b0

Original comment by marco.ha...@gmail.com on 31 Oct 2011 at 5:14

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorry, but that fingerprint is already known. Thanks regardless though. The
known fingerprints are:

"2c:b4:86:a8:da:87:77:3f:e4:b2:9d:26:6e:11:9e:00:3d:db:85:55",
"b0:36:f6:fd:0b:6f:28:75:ca:3b:5d:4a:91:07:ce:db:d0:0d:71:b0"

Original comment by sca...@gmail.com on 31 Oct 2011 at 5:53

GoogleCodeExporter commented 9 years ago 
For what it's worth, I can send right now and the fingerprint is: ‎09 37 b0 
df 67 b6 01 dd 2a b6 0b b1 f9 24 0f 3c 3f 77 77 2f

Original comment by sogn...@gmail.com on 31 Oct 2011 at 10:39

GoogleCodeExporter commented 9 years ago 
Did you send via wifi or 3g? This keeps getting weirder.
Am 31.10.2011 23:40 schrieb <websmsdroid@googlecode.com>:

Original comment by sca...@gmail.com on 1 Nov 2011 at 12:39

GoogleCodeExporter commented 9 years ago 
There might be some load balanced involved.

Original comment by f...@ub0r.de on 1 Nov 2011 at 7:41

GoogleCodeExporter commented 9 years ago 
I had the same problem. I found my browser to be using the

09:37:b0:df:67:b6:01:dd:2a:b6:0b:b1:f9:24:0f:3c:3f:77:77:2f

that was already mentioned in comment 23. After adding the fingerprint to the 
plugin (and rebuilding) it works for me:

https://github.com/lmb/websms-connector-o2/pull/1

(I found this issue after my first push, so this first removes and than re-adds 
the old fingerprint).

Original comment by boris-c...@gmx.com on 1 Nov 2011 at 10:28

GoogleCodeExporter commented 9 years ago 
I merged your changes and pushed a new APK to the market. Thanks for your 
assistance Boris! Let's hope we're done with this.

Original comment by sca...@gmail.com on 1 Nov 2011 at 11:49

GoogleCodeExporter commented 9 years ago 
Works fine so far. 
Is that setting which was mentiond as broken in comment #20 fixed, too already?

Original comment by sogn...@gmail.com on 3 Nov 2011 at 12:40

GoogleCodeExporter commented 9 years ago

Original comment by f...@ub0r.de on 6 Nov 2011 at 1:39