Package: symfony
Version: 2.3.21+dfsg-4+deb8u4
CVE ID : CVE-2017-16652 CVE-2017-16654 CVE-2018-11385 CVE-2018-11408
CVE-2018-14773 CVE-2018-19789 CVE-2018-19790
Several security vulnerabilities have been discovered in symfony, a PHP
web application
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Mar 2019 09:20:42 -0500
Source: symfony
Binary: php-symfony-browser-kit php-symfony-class-loader
php-symfony-classloader php-symfony-config php-symfony-console
php-symfony-css-selector php-symfony-debug
Control: notfound -1 232-25+deb9u9
Control: notfound -1 241-1
Hi Will
Am 09.03.19 um 00:14 schrieb Will Roberts:
> Package: systemd
> Version: 215-17+deb8u10
> Severity: important
> Tags: patch
>
> Dear Maintainer,
>
> The fix for CVE-2018-16864 contains a memory leak that was fixed for
>
Amend (self-answer):
Answers to some of my questions are found in
https://debian-handbook.info/browse/stable/sect.release-lifecycle.html#id-1.4.9.15
(section "Lifecycle of a Release")
Hi,
On 09/03/2019 11:44, th.pitsc...@uni.de wrote:
> Hello list members,
>
> is it correct to assume that in Debian versions entering "obsolete"
> state, any "aptitude safe-upgrade" will stop upgrading to newer
> packages other than for the reason of security fixes?
>
> When exactly would also
Hello list members,
is it correct to assume that in Debian versions entering "obsolete"
state, any "aptitude safe-upgrade" will stop upgrading to newer
packages other than for the reason of security fixes?
When exactly would also the security related upgrades stop?
In other words: what are the
