More food for thought.
https://mobile.twitter.com/pwnallthethings/status/947978927284383744
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
Sorry, cpuid.
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Message-
From: Kurt Jaeger
Sent: 02/01/2018 21:41
To: C
Hi!
> You can see if your cpu supports pcid using cpuinfo from ports.
portfind cpuinfo
finds sysutils/p5-Linux-Cpuinfo, but this does not provide a cpuinfo
command ?
--
p...@opsec.eu+49 171 3101372 2 years to go !
On January 2, 2018 4:56:48 PM PST, Michael Butler
wrote:
>On 01/02/18 19:20, Cy Schubert wrote:
>> This Linux commit gives us a hint.
>>
>> https://lkml.org/lkml/2017/12//27/2
>
>Sadly, the articles I've read to date make no mention of which Intel
>silicon revs are vulnerable. However, the use o
On 01/02/18 19:20, Cy Schubert wrote:
> This Linux commit gives us a hint.
>
> https://lkml.org/lkml/2017/12//27/2
Sadly, the articles I've read to date make no mention of which Intel
silicon revs are vulnerable. However, the use of the PCID feature, which
is only available on more recent CPUs, d
On January 2, 2018 4:24:55 PM PST, Cy Schubert wrote:
>https://mobile.twitter.com/grsecurity/status/948170302286172160?p=v
>
>---
>Sent using a tiny phone keyboard.
>Apologies for any typos and autocorrect.
>Also, this old phone only supports top post. Apologies.
>
>Cy Schubert
> or
>The need of
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Message-
From: Zaphod Beeblebrox
Sent: 02/01/2018 15:50
To: Michael
https://mobile.twitter.com/grsecurity/status/948170302286172160?p=v
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Messa
This Linux commit gives us a hint.
https://lkml.org/lkml/2017/12//27/2
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original M
The register article says the specifics are under embargo still. That would
make it hard for anybody working with Intel to comment publicly on the flaw
and any mitigations that may be underway. It would be unwise to assume that
all the details are out until the embargo lifts.
Warner
On Jan 2, 201
>From the information that was leaked by AMD claiming that their processors
didn't have the flaws, it would seem any OS in which the kernel occupies
the same address space as the userland would be vulnerable. The AMD post
implied that Intel's speculative execution of code did not check the
validit
Has any impact assessment been made as to FreeBSD's exposure or
mitigation strategies?
'Kernel memory leaking' Intel processor design flaw forces Linux,
Windows redesign - The Register
Other OSes will need an update, performance hits loom A fundamental
design flaw in Intel's processor chips has f
On 2018-Jan-2, at 11:48 AM, Mark Millard wrote:
> I've seen this over many versions of head for months
> but have never managed to find a way to force it to
> happen. It just shows up once and a while.
>
> Thus, I'm just dumping out some top and kernel information
> here for reference. I've used
I've seen this over many versions of head for months
but have never managed to find a way to force it to
happen. It just shows up once and a while.
Thus, I'm just dumping out some top and kernel information
here for reference. I've used:
openssl speed 1>/dev/null 2>&1 &
openssl speed 1>/dev/null
On Tuesday, 2 January 2018 16:26:31 CET, Kurt Jaeger wrote:
Hi!
I've added one more printf to see what is coming as year from
BCD. The code
is attached below and bcd.year comes out as 24 (decimal) which
is 0x18. I.e. it
seems that the year from 2018 is stored in hex as 0x18, or?
It's actua
Hi!
> I've added one more printf to see what is coming as year from BCD. The code
> is attached below and bcd.year comes out as 24 (decimal) which is 0x18. I.e.
> it
> seems that the year from 2018 is stored in hex as 0x18, or?
It's actually BCD code:
https://en.wikipedia.org/wiki/Binary-coded_
El día martes, enero 02, 2018 a las 02:00:20p. m. +0100, Matthias Apitz
escribió:
> # cp /usr/obj/usr/src/sys/GENERIC/kernel /boot/kernel/kernel
>
> The kernel boots fine as:
>
> FreeBSD c720-r314251 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r314251M: Tue Jan
> 2 12:53:31 CET 2018 guru@c720-r3
On Tue, Jan 02, 2018 at 03:17:14PM +0100, Pierre DAVID wrote:
> On Mon, Jan 01, 2018 at 11:09:07PM +0200, Konstantin Belousov wrote:
> >clang issues a calls to libatomic, which we do not provide.
> >As a workaround, use the following command to compile. The resulting
> >binary works on all practic
On Mon, Jan 01, 2018 at 05:14:00PM -0800, Don Lewis wrote:
> Since lint was removed from 12.0-CURRENT, it is not possible to build
> 11.1-STABLE on a 12.0-CURRENT host, but I was able to work around that
> by copying /usr/bin/true to /usr/bin/lint. Unfortunately, that trick
> doesn't work when upd
On Mon, Jan 01, 2018 at 11:09:07PM +0200, Konstantin Belousov wrote:
On Mon, Jan 01, 2018 at 09:47:40PM +0100, Pierre DAVID wrote:
Hi,
I'm on a recent current:
FreeBSD biceps.ma.maison 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r327239: Wed
Dec 27 18:25:46 CET 2017
p...@biceps.ma.maison:/us
El día lunes, enero 01, 2018 a las 05:02:42p. m. -0700, Ian Lepore escribió:
> Okay, I've created a pair of patches for this. The first adds some
> common support routines usable by all RTC drivers with BCD hardware.
> The second one converts the atrtc driver to use those routines. The
> common
> On Mon, 2018-01-01 at 09:54 +0100, Matthias Apitz wrote:
> > El d?a domingo, diciembre 31, 2017 a las 10:19:50a. m. -0700, Ian Lepore
> > escribi?:
> >
> > >
> > > >
> > > > I will let the C720 over night under power while sitting in the boot
> > > > menu,
> > > > maybe this will fix the RTC
22 matches
Mail list logo
