math/pari updates (Math::Pari still gets updated but even recently
released versions require old Pari; the crypto libs based on this
seem a bit unloved these days).
ok daniel semarie
Since we don't build shared libraries, the CAST assembly implementation
is included on i386 even though there is no PIC version. Skip the whole
cipher as there are no SSL/TLS cipher suites that use CAST.
ok sthen@
- don't force-disable the use of BN_GENCB_new() and friends, supported
since LibreSSL 2.7.1
- fix WANTLIB, this is c++
- provide a correct WRKDIST, and use it
- install README.md, it has useful data
ok abieber@ (maintainer)
2.0.14 - Some Base64-encoded values couldn't be decoded when using unpadded variants. This has been fixed.
2.0.13 - Security fix: sodium_pad() used to read extra memory when given an empty string
DIRB is a Web Content Scanner. It looks for hidden Web Objects. It
basically works by launching a dictionary based attack against a web
server and analizing the response. DIRB main purpose is to help in web
application auditing.
ok rpointel@ a while ago
to match the visibility of max_align_t between C and C++.
GCC 4.9 defaults to C89 and does not accept the "restrict" keyword
by default. This causes a configure check to add -std=gnu99 to the
compiler flags. Since max_align_t is from C11, the -std=gnu99 flag
removes it from visibility and gnutls's copy of gnulib then provides
its own replacement definition of max_align_t. When gnutls builds
its C++ library, the C++ visibility rules are different. The
max_align_t from stddef.h reappears and collides with the gnulib
replacement.
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
libssl internals. This effectively takes the OpenSSL 1.1 code path
instead of the OpenSSL 1.0 code path, and will allow for further
libssl clean up.
with and OK jsing@
