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@
"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.
add an XXX comment for now as it needs a patch to cope with resolvd's
comment on the "nameserver" line; this is not new but i only noticed
when testing the update
which aren't used as dependencies in ports. many are either old stuff,
or things used to provide backports of functionality from newer Python
base versions which were used in ports that have already been converted
to py3-only.
