On Wed, May 29, 2019 at 10:33:59AM +, Mike Gabriel wrote:
> Hi Adrian, hi all other LTS contributors with Go knowledge,
Hi Mike,
> can anyone of you possibly take a closer look at golang-go.crypto [1] and
> triage CVE-2019-11840.
The only actual code change is in the assembler in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: miniupnpd
Version: 1.8.20140523-4+deb8u1
CVE ID : CVE-2017-1000494 CVE-2019-12107 CVE-2019-12108
CVE-2019-12109 CVE-2019-12110 CVE-2019-12111
Ben Barnea and colleagues from VDOO discovered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 19:03:02 +0200
Source: miniupnpd
Binary: miniupnpd
Architecture: source amd64
Version: 1.8.20140523-4+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Thomas Goirand
Changed-By: Thorsten Alteholz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: tomcat7
Version: 7.0.56-3+really7.0.94-1
CVE ID : CVE-2019-0221
Nightwatch Cybersecurity Research team identified a XSS vulnerability
in tomcat7. The SSI printenv command echoes user provided data without
escaping.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 28 May 2019 23:30:50 +0530
Source: tomcat7
Binary: tomcat7-common tomcat7 tomcat7-user libtomcat7-java libservlet3.0-java
libservlet3.0-java-doc tomcat7-admin tomcat7-examples tomcat7-docs
Architecture: source all
Version:
On 30/05/2019 09:37, Hugo Lefeuvre wrote:
> Hi,
>
> Apparently, wireshark 1.12.1+g01b65bf-4+deb8u19 failed to build on armel. I
> have absolutely no idea of what happened. At first glance it looks like tar
> segfaulted[0] :-)
>
> Is it possible to restart the build for armel?#
Given back.
Hi,
Apparently, wireshark 1.12.1+g01b65bf-4+deb8u19 failed to build on armel. I
have absolutely no idea of what happened. At first glance it looks like tar
segfaulted[0] :-)
Is it possible to restart the build for armel?
cheers,
Hugo
[0]
