On Wed, Mar 14, 2018 at 12:39:22PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 14 Mar 2018, Moritz Muehlenhoff wrote:
> > On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote:
> > > severity 887856 grave
> > > block 887856 by 886998
> > > thanks
> > >
> > > On Sat,
On Wed, 14 Mar 2018, Moritz Muehlenhoff wrote:
> On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote:
> > severity 887856 grave
> > block 887856 by 886998
> > thanks
> >
> > On Sat, 20 Jan 2018, Julien Aubin wrote:
> > > As of now intel-microcode of stretch is still set to
On Sun, Jan 21, 2018 at 07:47:35AM -0200, Henrique de Moraes Holschuh wrote:
> severity 887856 grave
> block 887856 by 886998
> thanks
>
> On Sat, 20 Jan 2018, Julien Aubin wrote:
> > As of now intel-microcode of stretch is still set to 20170707 (20171117
> > through
> > bpo) which lets users
Processing commands for cont...@bugs.debian.org:
> severity 887856 grave
Bug #887856 [intel-microcode] intel-microcode: Spectre / Meltdown : bring
intel-microcode 20180104 to stretch
Severity set to 'grave' from 'critical'
> block 887856 by 886998
Bug #887856 [intel-microcode] intel-microcode:
severity 887856 grave
block 887856 by 886998
thanks
On Sat, 20 Jan 2018, Julien Aubin wrote:
> As of now intel-microcode of stretch is still set to 20170707 (20171117
> through
> bpo) which lets users vulnerable to Spectre attack CVE-2017-5715. Could you
> please bring quickly the microcode
Package: intel-microcode
Version: 3.20171117.1~bpo9+1
Severity: critical
Tags: security
Justification: root security hole
Hi,
As of now intel-microcode of stretch is still set to 20170707 (20171117
through
bpo) which lets users vulnerable to Spectre attack CVE-2017-5715. Could you
please bring
6 matches
Mail list logo