HTTPS peer authentication issue.

mwarning / trigger

Android app to lock/unlock/ring doors. Supports generic HTTPS/SSH/Bluetooth/MQTT and Nuki Smartlock.

GNU General Public License v3.0

134 stars 22 forks source link

HTTPS peer authentication issue. #61

Closed zelch closed 3 years ago

zelch commented 3 years ago

When I setup trigger with a basic HTTPS URL for open/close, I get:

javax.net.ssl.SSLPeerUnverifiedException: Hostname: >my hostname< not verified: ...

Except, the certificate is valid, Chrome on the same device has no problem going to a URL on the same host, the CN matches, the Alt DNS list has the host name as well.

If I disable the hostname check, stuff works, but I can't see any reason why this should be necessary.

mwarning commented 3 years ago

Chrome might come with its own root certificates. Did you create that certificate on your own?

zelch commented 3 years ago

Nope, it's a fairly standard Let's Encrypt certificate.

mwarning commented 3 years ago

I was able to verifiy the problem. Fixed in https://github.com/mwarning/trigger/commit/713cfe5a2311ca4ea2b35c7d7898e00227e2cb14