I can only provide this shellcode right here.
\x89\xe1\xd9\xcd\xd9\x71\xf4\x5d\x55\x59\x49\x49\x49\x49\x49\x49" \
"\x49\x49\x49\x49\x43\x43\x43\x43\x43\x43\x37\x51\x5a\x6a\x41\x58" \
"\x50\x30\x41\x30\x41\x6b\x41\x41\x51\x32\x41\x42\x32\x42\x42\x30" \
"\x42\x42\x41\x42\x58\x50\x38\x41\x42\x75\x4a\
On 14 January 2016 at 14:29, farmdve wrote:
> Again, sorry for the personal message, Peter, Google really is failing here,
> more so than me.
There's a "Default reply behaviour" setting in Settings->General
in gmail that you can use to make it default to reply-to-all
rather than just reply if you
Again, sorry for the personal message, Peter, Google really is failing
here, more so than me.
>> But in my case, an instruction did forward modify some code, but this if
statement did not execute and QEMU executed the old code.
On 14 January 2016 at 16:28, farmdve wrote:
> But in my case, an in
On 14 January 2016 at 10:15, farmdve wrote:
> Sorry about that. Somehow Google decided it should reply to you, rather than
> the mailing list. It was an honest mistake.
>
> Original question is below
>
>
> I am unable to get this part here if (!(tb_end <= start || tb_start >= end))
> in tb_invalid
Sorry about that. Somehow Google decided it should reply to you, rather
than the mailing list. It was an honest mistake.
Original question is below
I am unable to get this part here if (!(tb_end <= start || tb_start >=
end)) in tb_invalidate_phys_page_range
What would happen if code forward mod
On 13 January 2016 at 16:45, farmdve wrote:
> On Windows, in software MMU mode, how does QEMU handle
> self-modifying code?
When we translate the guest code in a page of guest
memory, we mark that page as "not dirty for code" by
calling tlb_protect_code(), which clears a DIRTY_MEMORY_CODE
bit and
On Windows, in software MMU mode, how does QEMU handle self-modifying code?
Thank you.
