Hi
On Wed, Mar 30, 2022 at 09:31:32AM +, Holger Levsen wrote:
> On Wed, Mar 30, 2022 at 09:36:58AM +0200, Sylvestre Ledru wrote:
> > Le 30/03/2022 à 07:07, Salvatore Bonaccorso a écrit :
> > > Sylvestre and Holger, would you have time to include the bugfix as
> > > well in the future bullseye
On Wed, Mar 30, 2022 at 09:36:58AM +0200, Sylvestre Ledru wrote:
> Le 30/03/2022 à 07:07, Salvatore Bonaccorso a écrit :
> > Sylvestre and Holger, would you have time to include the bugfix as
> > well in the future bullseye point release?
> Sure, should be easy.
> Is there a timeline?
as the last
Le 30/03/2022 à 07:07, Salvatore Bonaccorso a écrit :
Sylvestre and Holger, would you have time to include the bugfix as
well in the future bullseye point release?
Sure, should be easy.
Is there a timeline?
Cheers,
Sylvestre
Hi all,
On Fri, Mar 25, 2022 at 02:57:12PM -0300, Leandro Cunha wrote:
> Hi,
>
> On Fri, Mar 25, 2022 at 2:38 PM Georgi Naplatanov wrote:
> >
> > On 3/25/22 19:19, Leandro Cunha wrote:
> > > Hi,
> > >
> > > On Fri, Mar 25, 2022 at 4:19 AM Georgi Naplatanov wrote:
> > >>
> > >> On 3/25/22
Hi,
On Fri, Mar 25, 2022 at 2:38 PM Georgi Naplatanov wrote:
>
> On 3/25/22 19:19, Leandro Cunha wrote:
> > Hi,
> >
> > On Fri, Mar 25, 2022 at 4:19 AM Georgi Naplatanov wrote:
> >>
> >> On 3/25/22 03:24, Leandro Cunha wrote:
> >>> Hi,
> >>>
> >>> On Wed, Mar 23, 2022 at 6:18 PM Georgi
On 3/25/22 19:19, Leandro Cunha wrote:
> Hi,
>
> On Fri, Mar 25, 2022 at 4:19 AM Georgi Naplatanov wrote:
>>
>> On 3/25/22 03:24, Leandro Cunha wrote:
>>> Hi,
>>>
>>> On Wed, Mar 23, 2022 at 6:18 PM Georgi Naplatanov wrote:
On 3/23/22 22:43, Leandro Cunha wrote:
> Hi,
>
>
Hi,
On Fri, Mar 25, 2022 at 4:19 AM Georgi Naplatanov wrote:
>
> On 3/25/22 03:24, Leandro Cunha wrote:
> > Hi,
> >
> > On Wed, Mar 23, 2022 at 6:18 PM Georgi Naplatanov wrote:
> >>
> >> On 3/23/22 22:43, Leandro Cunha wrote:
> >>> Hi,
> >>>
> >>> On Wed, Mar 23, 2022 at 2:33 PM Georgi
On 3/25/22 03:24, Leandro Cunha wrote:
> Hi,
>
> On Wed, Mar 23, 2022 at 6:18 PM Georgi Naplatanov wrote:
>>
>> On 3/23/22 22:43, Leandro Cunha wrote:
>>> Hi,
>>>
>>> On Wed, Mar 23, 2022 at 2:33 PM Georgi Naplatanov wrote:
On 3/23/22 18:35, piorunz wrote:
> On 23/03/2022 15:41,
Hi,
On Wed, Mar 23, 2022 at 6:18 PM Georgi Naplatanov wrote:
>
> On 3/23/22 22:43, Leandro Cunha wrote:
> > Hi,
> >
> > On Wed, Mar 23, 2022 at 2:33 PM Georgi Naplatanov wrote:
> >>
> >> On 3/23/22 18:35, piorunz wrote:
> >>> On 23/03/2022 15:41, Leandro Cunha wrote:
> >>>
> Please, take
On 3/23/22 23:36, Salvatore Bonaccorso wrote:
> Hi,
>
> On Wed, Mar 23, 2022 at 11:17:41PM +0200, Georgi Naplatanov wrote:
>> On 3/23/22 22:43, Leandro Cunha wrote:
>>> Hi,
>>>
>>> On Wed, Mar 23, 2022 at 2:33 PM Georgi Naplatanov wrote:
On 3/23/22 18:35, piorunz wrote:
> On
Hi,
On Wed, Mar 23, 2022 at 11:17:41PM +0200, Georgi Naplatanov wrote:
> On 3/23/22 22:43, Leandro Cunha wrote:
> > Hi,
> >
> > On Wed, Mar 23, 2022 at 2:33 PM Georgi Naplatanov wrote:
> >>
> >> On 3/23/22 18:35, piorunz wrote:
> >>> On 23/03/2022 15:41, Leandro Cunha wrote:
> >>>
>
On 3/23/22 22:43, Leandro Cunha wrote:
> Hi,
>
> On Wed, Mar 23, 2022 at 2:33 PM Georgi Naplatanov wrote:
>>
>> On 3/23/22 18:35, piorunz wrote:
>>> On 23/03/2022 15:41, Leandro Cunha wrote:
>>>
Please, take into consideration what is in the link and you can
consult through
it
Hi,
On Wed, Mar 23, 2022 at 2:33 PM Georgi Naplatanov wrote:
>
> On 3/23/22 18:35, piorunz wrote:
> > On 23/03/2022 15:41, Leandro Cunha wrote:
> >
> >> Please, take into consideration what is in the link and you can
> >> consult through
> >> it about CVE:
On 3/23/22 18:35, piorunz wrote:
> On 23/03/2022 15:41, Leandro Cunha wrote:
>
>> Please, take into consideration what is in the link and you can
>> consult through
>> it about CVE: https://security-tracker.debian.org/tracker/CVE-2017-5715
>
> Leandro,
> I've been on this website before I posted
On 23/03/2022 15:41, Leandro Cunha wrote:
Please, take into consideration what is in the link and you can consult through
it about CVE: https://security-tracker.debian.org/tracker/CVE-2017-5715
Leandro,
I've been on this website before I posted with spectre-meltdown-checker
results. I have
On 3/23/22 17:41, Leandro Cunha wrote:
> Hi,
>
> On Wed, Mar 23, 2022 at 11:47 AM Georgi Naplatanov wrote:
>>
>> On 3/23/22 15:58, piorunz wrote:
>>> On 12/03/2022 09:48, Georgi Naplatanov wrote:
>>>
spectre-meltdown-checker script reports that my system is vulnerable to
Hi,
On Wed, Mar 23, 2022 at 11:47 AM Georgi Naplatanov wrote:
>
> On 3/23/22 15:58, piorunz wrote:
> > On 12/03/2022 09:48, Georgi Naplatanov wrote:
> >
> >> spectre-meltdown-checker script reports that my system is vulnerable to
> >> CVE-2017-5715. My CPU is Intel(R) Core(TM) i7-8700 CPU @
On 3/23/22 15:58, piorunz wrote:
> On 12/03/2022 09:48, Georgi Naplatanov wrote:
>
>> spectre-meltdown-checker script reports that my system is vulnerable to
>> CVE-2017-5715. My CPU is Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
>>
>> Is this normal?
>>
>> In the past all checks from
On 12/03/2022 09:48, Georgi Naplatanov wrote:
spectre-meltdown-checker script reports that my system is vulnerable to
CVE-2017-5715. My CPU is Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Is this normal?
In the past all checks from spectre-meltdown-checker were green (my
system was not
19 matches
Mail list logo
