[Users] X86_BUG_CPU_INSECURE

[Сергей Мамонов]

Thanks a lot!

2018-01-06 14:40 GMT+03:00 Vasily Averin <vvs at virtuozzo.com>:

> We have released fixed RHEL6-based kernel,
> please update your nodes to 2.6.32-042stab127.2 kernel
>
> Thank you,
>         Vasily Averin
>
> On 2018-01-04 06:03, Alex Kobets wrote:
> > Hi,
> >
> >
> > Virtuozzo will release the kernel with fix asap.
> >
> > We have it under testing right now
> >
> >
> > Thank you,
> >
> > Alex
> >
> > ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------
> > *From:* users-bounces at openvz.org <users-bounces at openvz.org> on behalf
> of Hristo Benev <foxb at abv.bg>
> > *Sent:* Wednesday, January 3, 2018 6:39:10 PM
> > *To:* zoobab at gmail.com; OpenVZ users
> > *Subject:* Re: [Users] X86_BUG_CPU_INSECURE
> >
> >>-------- Оригинално писмо --------
> >>От: Benjamin Henrion zoobab at gmail.com
> >>Относно: [Users] X86_BUG_CPU_INSECURE
> >>До: "OpenVZ users list. This is THE list you need." <users at openvz.org>
> >>Изпратено на: 03.01.2018 03:02
> >
> >
> >> Hi,
> >>
> >> Just reading this:
> >>
> >> https://amp.reddit.com/r/sysadmin/comments/7nl8r0/intel_bug_incoming/
> >>
> >> Xen seems to have a pending patch to be release this week, but people
> >> are speculating now that you could bypass the entire isolation process
> >> provided by any hypervisor.
> >>
> >> Wait and see how this will be exploited, but you can be sure there
> >> will be exploits soon in the wild.
> >>
> >> The patch for software mitigation seems to be big and performance
> impacting.
> >>
> >> But that would probably mean that containers can be bypassed.
> >>
> >> Wait and see,
> >>
> >> --
> >> Benjamin Henrion (zoobab)
> >> Email: zoobab at gmail.com
> >> Mobile: +32-484-566109
> >> Web: http://www.zoobab.com
> >> FFII.org Brussels
> >> "In July 2005, after several failed attempts to legalise software
> >> patents in Europe, the patent establishment changed its strategy.
> >> Instead of explicitly seeking to sanction the patentability of
> >> software, they are now seeking to create a central European patent
> >> court, which would establish and enforce patentability rules in their
> >> favor, without any possibility of correction by competing courts or
> >> democratically elected legislators."
> >> _______________________________________________
> >> Users mailing list
> >> Users at openvz.org
> >> https://lists.openvz.org/mailman/listinfo/users
> >
> >
> > https://spectreattack.com
> >
> > States that OpenVZ might be affected.
> > _______________________________________________
> > Users mailing list
> > Users at openvz.org
> > https://lists.openvz.org/mailman/listinfo/users
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at openvz.org
> > https://lists.openvz.org/mailman/listinfo/users
> >
>
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://lists.openvz.org/mailman/listinfo/users
>



-- 
Best Regards,
Sergey Mamonov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20180106/f7757167/attachment.html>