On 27 February 2018 at 15:36, Davide Davini wrote:
> Hi,
>
> I'd like to know too. Maybe I missed something but as I understand it there
> are only patches on 11-stable now, is that correct?
The change is committed to stable/11, and a patch against 11.1 is
available for testing now. Kostik posted
Hi,
I'd like to know too. Maybe I missed something but as I understand it there
are only patches on 11-stable now, is that correct?
Is 10 ever going to be patched?
On Wed, Jan 31, 2018 at 10:27 AM, Zahrir, Abderrahmane <
abderrahmane.zah...@ca.com> wrote:
> Hi Guys,
>
> I understand that you ha
In message , "Zahrir, Abderrahmane" wrote:
>Hi Guys,
>
>I understand that you have not been notified early enough about the Meltdown
>and spectre security {flaws}...
Apparently, it wasn't just the FreeBSD security crew that was inappropriately
kept in the dark about this gaggle of hardware secu
Hi Guys,
I understand that you have not been notified early enough about the Meltdown
and spectre security flow.
However do we have a rough estimate (something like an approximate month) of
when a patch will be available for the latest version 11.1 and possibly 11.0?
Regards, Dahman
___
On Tue, Jan 16, 2018 at 07:31:43AM -0800, Gordon Tetlow wrote:
> On Tue, Jan 16, 2018 at 1:57 AM, Konstantin Belousov
> wrote:
> > On Mon, Jan 15, 2018 at 09:20:24PM -0800, Gordon Tetlow wrote:
> >> On Sat, Jan 13, 2018 at 8:10 AM, Konstantin Belousov
> >> wrote:
> >> > On Mon, Jan 08, 2018 at 09
On Tue, Jan 16, 2018 at 1:57 AM, Konstantin Belousov
wrote:
> On Mon, Jan 15, 2018 at 09:20:24PM -0800, Gordon Tetlow wrote:
>> On Sat, Jan 13, 2018 at 8:10 AM, Konstantin Belousov
>> wrote:
>> > On Mon, Jan 08, 2018 at 09:57:51AM -0800, Gordon Tetlow wrote:
>> >> Meltdown (CVE-2017-5754)
>> >> ~
On Mon, Jan 15, 2018 at 09:20:24PM -0800, Gordon Tetlow wrote:
> On Sat, Jan 13, 2018 at 8:10 AM, Konstantin Belousov
> wrote:
> > On Mon, Jan 08, 2018 at 09:57:51AM -0800, Gordon Tetlow wrote:
> >> Meltdown (CVE-2017-5754)
> >>
> >> Initial work can be tracked at https://
On Sat, Jan 13, 2018 at 8:10 AM, Konstantin Belousov
wrote:
> On Mon, Jan 08, 2018 at 09:57:51AM -0800, Gordon Tetlow wrote:
>> Meltdown (CVE-2017-5754)
>>
>> Initial work can be tracked at https://reviews.freebsd.org/D13797.
>> Please note this is a work in progress and s
On Mon, Jan 08, 2018 at 09:57:51AM -0800, Gordon Tetlow wrote:
> Meltdown (CVE-2017-5754)
>
> Initial work can be tracked at https://reviews.freebsd.org/D13797.
> Please note this is a work in progress and some stuff is likely to be
> broken.
I consider this patch as ready
On 12 January 2018 at 05:36, Zahrir, Abderrahmane
wrote:
> Hi Gordon,
>
> Is it possible to include me in your distribution list so that I can get
> notified when the FreeBSD patch is available.
The best way ensure you'll be notified when the changes are available
as a patch or SA for releases i
At 11:26 AM 1/12/2018, Mike Tancsa wrote:
"The code will be selectable via a tunable which ..." Perhaps wait for
the final product.
---Mike
Yes, I will be eagerly awaiting the final patch! In the meantime, I
have located some architectural information about the latest Intel
Atoms wh
On 1/12/2018 1:07 PM, Brett Glass wrote:
> All:
>
> The fix in this patch appears to be unconditional.
The original email said
"The code will be selectable via a tunable which ..." Perhaps wait for
the final product.
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Se
All:
The fix in this patch appears to be unconditional.
I do a lot of work with embedded Intel Atom processors, which do
not implement speculative execution. (Only one of them even
implements limited out-of-order execution.) These systems aren't
terribly powerful by today's standards, and wou
The test patch is here: https://reviews.freebsd.org/D13797
On Friday, January 12, 2018, Zahrir, Abderrahmane <
abderrahmane.zah...@ca.com> wrote:
> Hi Gordon,
>
> Is it possible to include me in your distribution list so that I can get
> notified when the FreeBSD patch is available.
>
> Regards,
Hi Gordon,
Is it possible to include me in your distribution list so that I can get
notified when the FreeBSD patch is available.
Regards, Dahman
___
freebsd-security@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
On 2018-Jan-10 16:46:01 +0530, Sujit K M wrote:
>>From my understanding what is happening is that an array overflow is
>>happening.
>Can't it be handled more generically.
The array overflow in the example code is solely a convenient mechanism to
make C reference an arbitrary virtual address. An
> Meltdown (CVE-2017-5754)
>
> In terms of priority, the first step is to mitigate against the Meltdown
> attack (CVE-2017-5754, cited as variant 3 by Project Zero). Work for
> this is ongoing, but due to the relatively large changes needed, this is
> going to take a little
On 1/8/18, Gordon Tetlow wrote:
> By now, we're sure most everyone have heard of the Meltdown and Spectre
> attacks. If not, head over to https://meltdownattack.com/ and get an
> overview. Additional technical details are available from Google
> Project Zero.
> https://googleprojectzero.blogspot.c
Thanks very much for the updates!
---Mike
On 1/8/2018 12:57 PM, Gordon Tetlow wrote:
> By now, we're sure most everyone have heard of the Meltdown and Spectre--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1
19 matches
Mail list logo
