The change in base relating to emulated thread-local-storage used by
OpenBSD (r1.2 of gnu/llvm/compiler-rt/lib/builtins/emutls.c) results in
an undefined symbol __emutls_get_address if the old binaries are used.
| $ nm -s libisc-9.16.23.so.old | grep __emutls_get_address
| U __emutls_get_address
| $ nm -s libisc-9.16.23.so.new | grep __emutls_get_address
| 00081a40 W __emutls_get_address
Other ports may be affected by this too but I have no idea how to find
them, if anyone gets the following at runtime from other packages
then it is likely to be the same issue and those will need bumps too:
undefined symbol '__emutls_get_address'
ld.so: named: lazy binding failed!
This has slightly less ancient TLS support (allowing us to get rid of
use of openssl to build) but is not compatible with older versions.
The warning remains; if you are still using this it is recommended that
you don't:
WARNING: NRPE is deprecated upstream and no longer receives bug fixes or
new features. For some of the checks on remote servers that you might
otherwise make using NRPE, you may like to consider "manubolon-snmp" and
an SNMP daemon instead.
github.com/willamowius/ptlib as advised by the gnugk project.
Set up CONFIGURE_ARGS as documented at
https://www.gnugk.org/gnugk-manual-14.html
This also has the nice side effect to unbreak with OpenSSL 1.1.1 where DH and
BIO are opaque (req. by tb@).
opendnssec assumes that all ldns >=1.7 have Ed25519/Ed448 but this isn't
correct. In ldns >= 1.8 the constants related to Ed25519/Ed448 are _not_
available unless those features are available, so builds trying to use
them will fail (previously this was a runtime failure).
opendnssec's autoconf script sets USE_ED25519/USE_ED448 (hardcoded to 1)
but doesn't actually use them in code. Change the code to use them, and
hardcode to 0 for now. Should check LDNS_BUILD_CONFIG_USE_ED25519 and
LDNS_BUILD_CONFIG_USE_ED448 on 1.8+.
litterbox is a TLS-only IRC logger. It logs events from IRC in a
SQLite database, indexing messages for full-text search. It is
intended for use with the IRC bouncer pounce, but can also be used
independently as a logging bot.
OK sthen@
pounce is a multi-client, TLS-only IRC bouncer. It maintains a
persistent connection to an IRC server, acting as a proxy and buffer for
a number of clients. When a client connects, any messages received
since it last disconnected will be relayed to it. Unlike some other
bouncers, pounce uses a single buffer for all IRC messages, which acts
as a queue from which each client reads messages independently.
OK kn@ and sthen@
This used to work but the flag name has changed in the past. riscv64 is
the only affected arch since its native support is limited to LLInt (and
that one fails to link on OpenBSD).
ok ajacoutot@ (maintainer)
currently unmaintained, and repository is archived and read-only
instead of waiting that things break or people to be unhappy that it
doesn't work as well they want, remove it from ports
ok sthen@
The configure script defines OPENSSL_BIN to "/usr/bin/openssl" on
OpenBSD; the default is "openssl".
Practically no difference on systems with just one openssl(1) in PATH,
but correct and configure might gain stuff in the future.
