Hi,
You're mixing up versions, packages, and releases.
> DSA 3503 was fixed in Wheezy version 3.2.73-2+deb7u3
DSA-3503 was fixed in linux version 3.2.73-2+deb7u3
> dsa-3514 was fixed in Wheezy version 2:3.6.6-6+deb7u7
DSA-3514 was fixed in samba version 2:3.6.6-6+deb7u7
> DSA 3511 was fixed
On 29/11/2017 17:09, Jonathan Hutchins wrote:
When doing an in-release upgrade it's usually not necessary to do
"upgrade" first, then "full-upgrade" (equivalent to dist-upgrade).
that is true, but I prefer to do an "upgrade" first because it is
"safer" (it don't remove other packages) and tha
The kernel package versions can be difficult to sort out, but anything
more recent than the fix date/version will have the fix. It is usually
applied to the current kernel version across all supported releases,
although testing and unstable can lag behind.
What I do is pretty common, aptitude upd
Look at the very bottom of the page you cited: "For the stable
distribution (jessie), these problems have been fixed in version
3.16.7-ckt20-1+deb8u4. CVE-2013-4312, CVE-2015-7566, CVE-2015-8767 and
CVE-2016-0723 were already fixed in DSA-3448-1. CVE-2016-0774 does not
affect the stable distributio
On 28/11/2017 21:40, P P wrote:
for example https://www.debian.org/security/2016/dsa-3503 for DSA 3503. But the
link doesn't tell which patch to install to fix the bug of DSA 3503.
if you look in the CVE link you find if there is a patch and where is
it, ... for example if you open the first
Hi, All,
We found bugs of DSA 3503, DSA 3511, DSA 3514, DSA 3548 and more on our
Debian systems. Debian has site for each bug, for example
https://www.debian.org/security/2016/dsa-3503 for DSA 3503. But the link
doesn't tell which patch to install to fix the bug of DSA 3503. I am looking
fo
6 matches
Mail list logo
