Good day.
So glad to see PhantomJS coming back to life!
I've been using PhantomJS 2.1.1 for a while and it is absolutely capable of browsing all kinds of TLS-enabled sites, despite that the executable itself is not linked against libssl/libcrypto:
linux-vdso.so.1 (0x00007ffd354d1000)
libz.so.1 => /lib64/libz.so.1 (0x00007fbb1ff38000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fbb1fcf3000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fbb1fa55000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fbb1f851000)
librt.so.1 => /lib64/librt.so.1 (0x00007fbb1f649000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fbb1f42b000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fbb1f0a3000)
libm.so.6 => /lib64/libm.so.6 (0x00007fbb1ed58000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fbb1eb41000)
libc.so.6 => /lib64/libc.so.6 (0x00007fbb1e787000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbb2014f000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007fbb1e555000)
libbz2.so.1 => /usr/lib64/libbz2.so.1 (0x00007fbb1e338000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007fbb1e0f5000)
With the latest release 2.1.3 however, the executable is now dynamically linked against libssl and libcrypto:
./phantomjs: /usr/lib64/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./phantomjs)
./phantomjs: /usr/lib64/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by ./phantomjs)
The trouble is that I have to run phantomjs across a diverse selection of Linux distributions, and not all of them satisfy those library dependencies.
So would there be a way to build PhantomJS without linking to those libraries, and still be able to browse TLS-enabled sites with the result executable?
Many thanks.
Kind regards,