constants from ldns for a different purpose, that ldns doesn't really
want to expose on non-EdXXX builds.
Bodge it in ldns instead by supporting the same USE_EDxxx cpp macros
that opendnssec uses. Looks to me like ldns are trying to replace them
with something harder to mess about with.
Hopefully the various parts of nlnetlabs responsible for these two
pieces of software will talk to each other and figure something out.
Hopefully this should fix ed25519 with opendnssec as found by an
anonymous reporter on ports@.
- llvm 13 fix: correct destructor signature
- more accurate HOMEPAGE, previous is now broken
- respect CFLAGS/CXXFLAGS instead of clobbering them
- fix tests with a ninjutsu trick
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+.
is defined then the SCT struct exists. Beck added OPENSSL_NO_CT to
opensslfeatures.h but the struct will only exist after the next bump.
Reported by & ok aja semarie
HVAC allows accessing secrets stored in a Vault directly from
Python code.
An access token must be created first, using a separate tool
like vault or vault-client.
ok sthen@
are outdated. ok benoit@ ajacoutot@
These are library classes written in PHP for various functionality and
used to be needed to support PHP applications in the ports tree (things
like roundcube, horde and others used them) but all of this type of
software in ports now uses bundled dependencies. For development,
typically a language-specific dependency manager (like www/composer)
is used rather than OS packages.
www/pear (providing pear itself and pear-utils) is still kept.
+- if err := protect.Pledge("stdio rpath wpath cpath tty proc exec"); err != nil {
++ if err := protect.Pledge("stdio rpath wpath cpath fattr tty proc exec"); err != nil {
during "gopass fsck" if files or directories are encountered with
permissions that are too wide, it will use syscall.Chmod to fix too-open
permissions on files or directories. wpath is not enough for this, fattr
is needed.
