Problem with GPS reverse Lookup

[Wayne Heming]

Hi Guys

I have noticed recently that the GPS reverse seems to be broken. Not sure at which version or even if its a Subsurface error or not.
I know it has worked in the past as my dive sites always populated some fields when I press the GPS (blue globe) icon.
The preferences are set up for Georeference as Country/State/Town

It produces an error at the bottom in RED, another message flashes past before the error but too fast to see.
There are messages in the error log attached. SSL handshake failed.
I tried the URL's listed in the ERROR (log file) directly and it seems that the api.geonames.org certificate is invalid, (net::ERR_CERT_COMMON_NAME_INVALID), Standard Windows asks to proceed, Yes, then displays information.

Version 6.0.5525-CICD-release (Windows 11)
Updated to
Version 6.0.5576-CICD-release 
Same error

--

Regards,

Wayne Heming
0428 436 638
wayne....@hemnet.com.au
http://dive.hemnet.com.au

[JB2Cool]

This is a problem for geonames.org to fix on their side then, only they can sort out their certificate. I have reported this for you via their mailing list.

Jason

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/b696f353-3ad2-4c56-827b-5a3fbcbe87e3%40hemnet.com.au.

[Wayne Heming]

Thank you 

To view this discussion visit https://groups.google.com/d/msgid/subsurface-divelog/CACuYfN6FiP6rzqdpzCiwMJpwV%3Dd1agvt76bKnYNTQiemFNY1oA%40mail.gmail.com.

[João Ventura]

Hi,

Not sure if the problem is solely with geonames. True, their certificate is no longer valid for api.geonames.org, so the following lookups fail:

https://api.geonames.org/oceanJSON?lang=en&lat=27.8142&lng=33.92&radius=50&username=dirkhh
https://api.geonames.org/findNearbyPlaceNameJSON?lang=en&lat=27.8142&lng=33.92&radius=50&username=dirkhh
https://api.geonames.org/findNearbyJSON?lang=en&lat=27.8142&lng=33.92&radius=50&username=dirkhh

However, if the same lookups are done to secure.geonames.org, they all succeed:

https://secure.geonames.org/oceanJSON?lang=en&lat=27.8142&lng=33.92&radius=50&username=dirkhh
https://secure.geonames.org/findNearbyPlaceNameJSON?lang=en&lat=27.8142&lng=33.92&radius=50&username=dirkhh
https://secure.geonames.org/findNearbyJSON?lang=en&lat=27.8142&lng=33.92&radius=50&username=dirkhh

Also, it seems from https://groups.google.com/g/geonames/c/98M7YgpW0Es/m/ZkRyop5iBgAJ that the SSL API endpoint is indeed secure.geonames.org. If this is confirmed, the change should be done in subsurface, and not in geonames. I've created issue #4775 in Github, and submitted a pull request to fix this at https://github.com/subsurface/subsurface/pull/4776

Cheers,

João Ventura

[João Ventura]

The https://github.com/subsurface/subsurface/pull/4778 pull request that solves this has been merged, so the next version of subsurface should have this fixed as per the documentation (using secure...), even if in the meantime the geonames.org team fixes their certificate.