This comes from a new upstream, that focused on moving fwbuilder from
Qt4 to Qt5. There is no other functional changes to be expected by this
update.
OK rsadowski@
letsencrypt have already stopped allowing ACMEv1 for new domain
validations, and are now doing "brownouts" for all ACMEv1 access,
disabling it temporarily twice a month for increasing lengths of
time (6/24/48/72/120/168 hours) in the run up to disabling it
completely on June 1st.
Information for inst:py3-argon2-cffi-20.1.0
Comment:
argon2 password hashing for Python
Description:
Argon2 is a secure password hashing algorithm. Is is designed to
have both a configurable runtime as well as memory consumption.
The current workhorses of password hashing are unquestionably bcrypt
and PBKDF2. And while they're still fine to use, the password
cracking community embraced new technologies like GPUs and ASICs
to crack passwords in a highly parallel fashion.
An effective measure against extreme parallelism proved making
computation of password hashes also memory hard.
Between 2012 and 2015, the password hashing competition took place
to find a new, secure, and future-proof password hashing algorithm.
The winner of this competition was announced as Argon2.
Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
WWW: https://argon2-cffi.readthedocs.io/
value (128) as discussed with kettenis@. turns out, the code to detect this on
the fly doesn't seem to work properly on linux too.
ok landry@ (MAINTAINER)
__GLIBC_PREREQ() being available.
furthermore, for powerpc64 we need to disable the generated assembler code for
it fails to assemble with llvm:
error: unexpected token at start of statement: .0:
that is to be revisited but for now libnettle (and thus gnutls) can be built again.
ok aja@ (MAINTAINER)
As diagnosed by kettenis, running the regress/lib/libssl/interop/openssl
test results in a SIGILL or SIGBUS due to an alignment issue. The reason
for this is that the configure magic fails to pick up -m64 which is
needed for the perlasm to generate the correct flavor of assembly.
None of the approaches for setting variables in the main port Makefile
worked. Since we already patch out -O3 from Configure, I added -m64
there. The resulting binary seems to work well. The interop tests on
sparc64 pass with this patch.
Many thanks to kettenis for figuring this out and to sthen who helped
me save a lot of time with FLAVOR=no_man.
ok sthen
