-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Note: the current version of the following document is available here:
https://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c05369403
SUPPORT COMMUNICATION - SECURITY BULLETIN
Document ID: c05369403
Version: 1
HPSBGN03694 rev.1 - HPE
Folks,
I'm curious about whether folks are filtering ICMPv6 PTB<1280
and/or IPv6 fragments targeted to BGP routers (off-list datapoints are
welcome).
In any case, you mind find it worth reading to check if you're affected
(from Section 2 of recently-published RFC8021):
cut here
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
- -
Debian Security Advisory DSA-3760-1 secur...@debian.org
https://www.debian.org/security/ Moritz Muehlenhoff
January 12, 2017
Description of the potential vulnerability:Lack of appropriate exception
handling in some applications allows attackers to make a systemUI crash easily
resulting in a possible DoS attack
Affected versions: L(5.0/5.1), M(6.0), and N(7.0)
Disclosure status: Privately disclosed.
The patch prevents
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[slackware-security] bind (SSA:2017-011-01)
New bind packages are available for Slackware 13.0, 13.1, 13.37, 14.0, 14.1,
14.2, and -current to fix a security issue.
Here are the details from the Slackware 14.2 ChangeLog:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[slackware-security] gnutls (SSA:2017-011-02)
New gnutls packages are available for Slackware 14.0, 14.1, 14.2, and -current
to fix security issues.
Here are the details from the Slackware 14.2 ChangeLog:
+--+