Hello,
Am 18.06.2017 um 20:22 schrieb Philipp Hahn:
> Am 17.06.2017 um 18:51 schrieb Laszlo Ersek:
>> (I also recommend using the "vbindiff" tool for such problems, it is
>> great for picking out patterns.)
>>
>> ** ** ** ** ** ** ** ** 8 9 ** ** ** 13 14 15
>> -- -- -- -- -
* Philipp Hahn (h...@univention.de) wrote:
> Hello,
>
> Am 17.06.2017 um 18:51 schrieb Laszlo Ersek:
> > (I also recommend using the "vbindiff" tool for such problems, it is
> > great for picking out patterns.)
> >
> > ** ** ** ** ** ** ** ** 8 9 ** ** ** 13 14 15
> > -- --
Am 18.06.2017 um 20:27 schrieb Dr. David Alan Gilbert:
> * Philipp Hahn (h...@univention.de) wrote:
>> Hello,
>>
>> Am 17.06.2017 um 18:51 schrieb Laszlo Ersek:
>>> (I also recommend using the "vbindiff" tool for such problems, it is
>>> great for picking out patterns.)
>>>
>>> ** ** ** *
Hello,
Am 17.06.2017 um 18:51 schrieb Laszlo Ersek:
> (I also recommend using the "vbindiff" tool for such problems, it is
> great for picking out patterns.)
>
> ** ** ** ** ** ** ** ** 8 9 ** ** ** 13 14 15
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 01
On 06/16/17 19:03, Philipp Hahn wrote:
> Comparing the corrupted (left) with the supposed (right) driver shows
> the following pattern:
>> /tmp/uefi.bin [+] 15038,1 Alles
>> /tmp/uefi.ko [+]15038,1 Alles
>> 003ac00:
Hello,
I tried to get QEMU running with UEFI and SecureBoot. It sometimes
works, but sometimes I get memory corruption:
- the Debian installer sometimes fails to load the "libata.ko" or
"e1000.ko" modules.
- it it not always the same module
- my guest kernel uses KASLR, which might explain differe
