John-Mark Gurney wrote:
> Oliver Pinter wrote this message on Tue, Feb 17, 2015 at 23:27 +0100:
> > On Tue, Feb 17, 2015 at 11:19 PM, Fabian Keil
> > wrote:
> > > John-Mark Gurney wrote:
> > >
> > >> If you are running a current kernel r273872 or later, please upgrade
> > >> your kernel to r278
Oliver Pinter wrote this message on Tue, Feb 17, 2015 at 23:27 +0100:
> On Tue, Feb 17, 2015 at 11:19 PM, Fabian Keil
> wrote:
> > John-Mark Gurney wrote:
> >
> >> If you are running a current kernel r273872 or later, please upgrade
> >> your kernel to r278907 or later immediately and regenerate
On Tue, Feb 17, 2015 at 11:19 PM, Fabian Keil
wrote:
> John-Mark Gurney wrote:
>
>> If you are running a current kernel r273872 or later, please upgrade
>> your kernel to r278907 or later immediately and regenerate keys.
>
> I tried ...
>
> start_init: trying /sbin/init
> <118>[20] Setting hostuu
John-Mark Gurney wrote:
> If you are running a current kernel r273872 or later, please upgrade
> your kernel to r278907 or later immediately and regenerate keys.
I tried ...
start_init: trying /sbin/init
<118>[20] Setting hostuuid: [...]
<118>[20] Setting hostid: [...
[20]
[20]
[20] Fatal tra
On 17 February 2015 at 13:15, Ed Maste wrote:
>
> One other point - this only applies to keys generated while running on
> a kernel in that range. If you previously generated keys and then
> upgraded to r273872 or later there's no concern with respect to key
> randomness from this issue.
One furt
On 17 February 2015 at 12:37, John-Mark Gurney wrote:
> If you are running a current kernel r273872 or later, please upgrade
> your kernel to r278907 or later immediately and regenerate keys.
One other point - this only applies to keys generated while running on
a kernel in that range. If you pre
John-Mark Gurney wrote this message on Tue, Feb 17, 2015 at 09:37 -0800:
> If you are running a current kernel r273872 or later, please upgrade
> your kernel to r278907 or later immediately and regenerate keys.
>
> I discovered an issue where the new framework code was not calling
> randomdev_init
If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or later immediately and regenerate keys.
I discovered an issue where the new framework code was not calling
randomdev_init_reader, which means that read_random(9) was not returning
good random data. read_
