On Thu, Jun 9, 2016 at 12:55 PM, Theodore Ts'o wrote:
> On Thu, Jun 09, 2016 at 07:22:29PM +0200, PaX Team wrote:
>> > Well, the attacker can't control when the interrupts happen, but it
>> > could try to burn power by simply having a thread spin in an infinite
>> > loop ("0: jmp 0"), sure.
>>
>>
On Thu, Jun 09, 2016 at 07:22:29PM +0200, PaX Team wrote:
> > Well, the attacker can't control when the interrupts happen, but it
> > could try to burn power by simply having a thread spin in an infinite
> > loop ("0: jmp 0"), sure.
>
> yes, that's one obvious way to accomplish it but even normal
On 7 Jun 2016 at 9:58, Theodore Ts'o wrote:
> On Tue, Jun 07, 2016 at 02:19:14PM +0200, PaX Team wrote:
> > (i believe that) latent entropy is found in more than just interrupt
> > timing, there're
> > also data dependent computations that can have entropy, either on a single
> > system or
> > a
On Tue, Jun 07, 2016 at 02:19:14PM +0200, PaX Team wrote:
> (i believe that) latent entropy is found in more than just interrupt timing,
> there're
> also data dependent computations that can have entropy, either on a single
> system or
> across a population of them.
It's not clear how much data
On 6 Jun 2016 at 19:13, Theodore Ts'o wrote:
> On Mon, Jun 06, 2016 at 09:30:12PM +0200, PaX Team wrote:
> >
> > what matters for latent entropy is not the actual values fed into the
> > entropy
> > pool (they're effectively compile time constants save for runtime data
> > dependent
> > computa
On Mon, Jun 06, 2016 at 09:30:12PM +0200, PaX Team wrote:
>
> what matters for latent entropy is not the actual values fed into the entropy
> pool (they're effectively compile time constants save for runtime data
> dependent
> computations) but the precise sequence of them. interrupts stir this s
On 6 Jun 2016 at 7:38, David Brown wrote:
> On Fri, Jun 03, 2016 at 07:42:52PM +0200, Emese Revfy wrote:
> >On Wed, 1 Jun 2016 12:42:27 -0700
> >Andrew Morton wrote:
> >
> >> I don't think I'm really understanding. Won't this produce the same
> >> value on each and every boot?
> >
> >No, because
On Mon, Jun 6, 2016 at 6:38 AM, David Brown wrote:
> On Fri, Jun 03, 2016 at 07:42:52PM +0200, Emese Revfy wrote:
>>
>> On Wed, 1 Jun 2016 12:42:27 -0700
>> Andrew Morton wrote:
>>
>>> On Tue, 31 May 2016 01:31:45 +0200 Emese Revfy
>>> wrote:
>>>
>>> > This plugin mitigates the problem of the ke
On Fri, Jun 03, 2016 at 07:42:52PM +0200, Emese Revfy wrote:
On Wed, 1 Jun 2016 12:42:27 -0700
Andrew Morton wrote:
On Tue, 31 May 2016 01:31:45 +0200 Emese Revfy wrote:
> This plugin mitigates the problem of the kernel having too little entropy
during
> and after boot for generating crypto
9 matches
Mail list logo
