We have moved to a new Sailfish OS Forum. Please start new discussions there.
2

ePassi (Android) - "Connection timeout" [not relevant]

asked 2018-06-06 22:05:34 +0200

raketti gravatar image

updated 2019-11-04 14:54:35 +0200

The App in question is available in the Jolla Store, so by all standards, it should be compatible with the Sailfish Android version. I've installed in on my J1, but entering the username and PW just gets me a "Connection timeout" -message every time.

I do have to note that I only use WLAN (busted my sim slot) at the moment on the phone, but it seems that there's some connection issues with the dalvik. I tried:

  • Restarting network connections - did not work
  • Reboot phonw - did not work
  • Stop/Start alien - did not work

Here's what I'm getting when trying to use the app:

06-06 19:07:43.489  8541  8559 W GooglePlayServicesUtil: Google Play Store is missing.
06-06 19:07:43.554  8541  8541 W GooglePlayServicesUtil: Google Play Store is missing.
06-06 19:07:43.666  8541  8567 W GooglePlayServicesUtil: Google Play Store is missing.
06-06 19:07:43.695  8221  8221 I ActivityManager: START {cmp=fi.eventbrokers.sporttipassimobile/.activities.LoginActivity u=0} from pid 8541
06-06 19:07:43.698  8541  8567 W GooglePlayServicesUtil: Google Play Store is missing.
06-06 19:07:43.726  8541  8567 W GooglePlayServicesUtil: Google Play Store is missing.
06-06 19:07:43.813  8541  8541 W GooglePlayServicesUtil: Google Play Store is missing.
06-06 19:07:43.957  8541  8567 W GooglePlayServicesUtil: Google Play Store is missing.
06-06 19:07:43.977  8541  8567 W GooglePlayServicesUtil: Google Play Store is missing.

Not sure if it's the messages above or below that worries me the most:

06-06 19:07:54.622  8541  8571 D OkHttp  : --> GET https://services.epassi.fi/api/v2/login http/1.1
06-06 19:07:54.622  8541  8571 D OkHttp  : --> END GET
06-06 19:07:54.789  8541  8571 D OkHttp  : <-- HTTP FAILED: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Since the Google Play Service thingys are merely warnings (at least that's what I belive the "W" stands for), but the HTTP error is D(eadly? :D)

EDIT 2018-06-08: I opened a support request from the ePassi website and linked this thread. Let’s see if they can do something about the issue, like developing a native version. ;)

EDIT 2018-06-11: I received a reply from their support and the statement is (roughly translated):

"Unfortunately this is a situation that cannot be helped, Sailfish cannot be used with ePassi App."

I will reply to them that the previous version worked just fine and after the update it stopped working, if they could probably roll back the version. This might also be an issue with the Sailfish Android emulation, os a ticket might be needed for Jolla also as it's clearly a communicaiton error between the app and the ePassi servers.

Edit 2019-11-04: Works fine with XA2

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by raketti
close date 2019-11-04 14:53:42.500087

Comments

Thanks, for reporting this problem. I can confirm the bug by reproducing it on my Jolla 1 and XperiaX phones. I have used the epassi more then half of year without problems until last spring, when I updated the latest version of epassi application.

javali ( 2018-06-09 22:58:05 +0200 )edit

Thanks for the input, would you by any chance remember the App version you used? I could just pick one version from the Store comments, but I can't guarantee that those have worked.

raketti ( 2018-06-11 10:05:47 +0200 )edit

1 Answer

Sort by » oldest newest most voted
2

answered 2018-07-26 13:58:06 +0200

javali gravatar image

updated 2018-07-26 15:04:23 +0200

I believe, that the SSLHandshakeException is caused by the certificate of services.epassi.fi, which is issued by DigiCert Global Root G2 certificate in certificate chain.

openssl s_client -connect services.epassi.fi:443
...
Certificate chain
 0 s:/CN=services.epassi.fi
   i:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=Thawte TLS RSA CA G1
 1 s:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=Thawte TLS RSA CA G1
   i:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root G2

Unfortunately it is missing for some reason in /opt/alien/system/etc/security/cacerts/ trusted root CA certificate path of Sailfish (2.2.0.29 Mouhijoki) android support.

I fixed it by downloading certificate, modifying it to similar form than others and copying it (as root) to path above as takimata do in https://together.jolla.com/question/183137/how-to-import-tls-certificate-into-android-support/

Here are the commands used:

curl -O https://www.tbs-certificats.com/issuerdata/DigiCert_Global_Root_G2.crt
openssl x509 -in DigiCert_Global_Root_G2.crt -noout -text >>DigiCert_Global_Root_G2.crt
openssl x509 -subject_hash_old -noout -in DigiCert_Global_Root_G2.crt
c90bc37d
mv DigiCert_Global_Root_G2.crt c90bc37d.0
scp c90bc37d.0 nemo@xxx.xxx.x.xx: 
ssh nemo@xxx.xxx.x.xx
devel-su
mv c90bc37d.0 /opt/alien/system/etc/security/cacerts/
edit flag offensive delete publish link more

Question tools

Follow
3 followers

Stats

Asked: 2018-06-06 22:05:34 +0200

Seen: 565 times

Last updated: Nov 04 '19