How didn’t I spot this one before now? Hydra uses OpenSSL. It also uses
mysql, so that’s now stated. Added a mirror and stylistic changes as
well.
ClosesHomebrew/homebrew#33230.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
So, yeah, Links has been using the system OpenSSL for secure
connections.
Additional optional dependencies based on what the configure script recommends,
and a mirror, and a test, and style changes.
ClosesHomebrew/homebrew#33233.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
OpenSSL dependency and style changes. Added a very basic test - Sadly
it can’t do much more than this without downloading rainbow tables,
which can take significant time and bandwidth.
ClosesHomebrew/homebrew#33236.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
The website download link keeps lagging endlessly for me, so I’ve
lobbed in a mirror here.
ClosesHomebrew/homebrew#33238.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
Style changes, new devel version & luajit dep and new openssl directory
and appropriate configuration options.
ClosesHomebrew/homebrew#33239.
Signed-off-by: Jack Nagel <jacknagel@gmail.com>
One of sane-backends internal executables taps the system libcrypto.
This fixes that by poking it onto our shipped OpenSSL. Additional style
updates as well, and a new mirror.
Even when not deliberately, actively configured with openssl enabled,
it picks up and leans on the system openssl anyway. This pokes it onto
our OpenSSL instead. All other changes are style tweaks, and an added
simple test.
```
/usr/local/bin/cardos-tool:
/usr/local/Cellar/opensc/0.14.0/lib/libopensc.3.dylib (compatibility
version 4.0.0, current version 4.0.0)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current
version 0.9.8)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version
1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 1213.0.0)
```
Technically, we’re skipping a release here. 5.06 was released earlier
today but has fatal errors when built against an OpenSSL that was built
without either sslv2 or sslv3. We obviously have left sslv3 intact for
now, but you only need one of the above disabled to error out here.
This is a known error and upstream’s recommendation is for everyone
with that configuration to temporarily jump on the beta builds.
