ntdll: enable CreateRemoteThread and RtlCreateUserThread for remote processes

[Mike Hearn]

On 7/16/06, Alexandre Julliard <julliard at winehq.org> wrote:
> Cloning a new thread is not going to help with this at all, since it still uses the
> Win32 context of the original thread, so it only makes things worse.

What then is the solution? A service thread? I think it'd be OK to
have the hijacked thread be holding a lock, as CreateThread doesn't
seem to wait on the newly created thread anywhere.

thanks -mike