[sorry for reposting but the original copy I got back had been truncated]
libssl has a new "feature"
implemented by:
crypto/openssl/ssl/t1_lib.c
672 /* Add padding to workaround bugs in F5 terminators.
673 * See
https://tools.ietf.org/html/draft-agl-tls-padding-03
On Mon, Mar 9, 2015 at 8:49 PM, Dmitry Morozovsky wrote:
> Dear colleagues,
>
> any thoughts we're vulnerable to this?
In memtest86 exists a rowhammer test -
http://www.passmark.com/forum/showthread.php?4836-MemTest86-v6-0-Beta-%282015-02-13-Update-Beta-testing-is-now-closed%29
.
>
> http://goog
I have a suggestion. As a simpler measure, would it be possible to
implement a test at boot time to determine whether the system is
vulnerable? I guess such a test would have to run in the kernel to get the
particular memory mapping required. The result would naturally emit a
kernel message, but it
On 03/09/15 22:37, Bakul Shah wrote:
> On Mon, 09 Mar 2015 20:46:19 - "Poul-Henning Kamp"
> wrote:
>> In message
>> <20150309202308.64dfbb...@mail.bitblocks.com>, Bakul Shah
>> writes:
>>> On Mon, 09 Mar 2015 19:52:04 - "Poul-Henning Kamp"
>>>
>> wrote:
>>
>>> Hopefully ECC memo
