imaplib2 is a threaded Python IMAP4 client. Based on RFC 3501 and
original imaplib module, this is a version of imaplib that uses threads
to allow full use of the IMAP4 concurrency features, and to de-couple a
user of imaplib from i/o lags, except where explicitly allowed.
Since ports/lang/gcc doesn't have riscv64 support yet this helps us
unlock a bunch of ports there. Disabling fortran/blas/lapack means that
some feature are missing. This is mitigated by numpy shipping a minimal
lapack copy translated to C.
libpurple:
* Fix a regression in purple_str_to_time.
XMPP:
* Fix a double free in jabber/message.c.
Pidgin:
* Fix the link to the support mailing list archive in the About Dialog.
from Brad Smith (MAINTAINER)
Committed with gconftool-2 tweak.
ok ian@ and solene@
2Geom is a C++ 2D geometry library geared towards robust processing of
computational geometry data associated with vector graphics. The primary design
consideration is ease of use and clarity.
Feedback and OK sthen@
"Lame cache can be abused to severely degrade resolver performance"
Exploitation of broken authoritative servers using a flaw in response
processing can cause degradation in BIND resolver performance. The way the
lame cache is currently designed makes it possible for its internal data
structures to grow almost infinitely, which may cause significant delays in
client query processing.
The purpose of a resolver's lame cache is to ensure that if an authoritative
server responds to a resolver's query in a specific broken way, subsequent
client queries for the same <QNAME, QTYPE> tuple do not trigger further
queries to the same server for a configurable amount of time. The lame cache
is enabled by setting the lame-ttl option in named.conf to a value greater
than 0. That option is set to lame-ttl 600; in the default configuration,
which means the lame cache is enabled by default.
Impact:
Authoritative-only BIND 9 servers are NOT vulnerable to this flaw.
A successful attack exploiting this flaw causes a named resolver to spend most
of its CPU time on managing and checking the lame cache. This results in
client queries being responded to with large delays, and increased likelihood
of DNS timeouts on client hosts.
they're annotated with a setuptools_scm[toml] in the requirements list
but there's no warning about it not being present, they just try to
create an egg-info dir with 0.0.0 instead of the proper version.
drop the explicit py-toml deps in those ports which had it previously,
suggested by aja@. ok aja kmos
