These are chat archives for IndySockets/Indy

26th
Apr 2016
davidpn
@davidpn
Apr 26 2016 03:49
If I use IdOpenSSLSetLibPath on Android, the SSL libraries should be loaded explicitly from that path, yes? So if they're not on that path, the load should fail?
Remy Lebeau
@rlebeau
Apr 26 2016 16:49
yes
davidpn
@davidpn
Apr 26 2016 21:07
then I'm at a loss to explain this: I'm giving IdOpenSSLSetLibPath a completely bogus path, and it returns handles for each of the SSL libraries
The "bogus" directory doesn't even exist
davidpn
@davidpn
Apr 26 2016 22:56
I'm assuming this is related:
https://bugreports.qt.io/browse/QTBUG-38291
Remy Lebeau
@rlebeau
Apr 26 2016 23:07
probably, and I did see mention of this issue the other day
davidpn
@davidpn
Apr 26 2016 23:08
it'll probably end up being a non-issue for us.. just unexpected :-)
Remy Lebeau
@rlebeau
Apr 26 2016 23:10
I expect it to be a huge issue, actually. With Android replacing OpenSSL with BoringSSL, but still using the same filenames for the libraries, it means people can't bundle OpenSSL libs on devices where BoringSSL breaks Indy.
davidpn
@davidpn
Apr 26 2016 23:10
oh crap
had forgotten that they're not renaming
Remy Lebeau
@rlebeau
Apr 26 2016 23:13
yeah. Sucks that they didn't rename, considering that they are making some pretty major changes to the OpenSSL API interface, so they probably should have renamed.
davidpn
@davidpn
Apr 26 2016 23:57
I've worked around the issue by modifying the names in IdSSLOpenSSLHeaders, and it attempts to load the rebuilt .so's, but the load fails with an illegal instruction, so I guess my rebuild process was faulty..
Remy Lebeau
@rlebeau
Apr 26 2016 23:59
let me know if you get it working, maybe we can host the files for Indy users to download
davidpn
@davidpn
Apr 26 2016 23:59
will do