-
Notifications
You must be signed in to change notification settings - Fork 35
Description
Hi Sylvain,
I'd like to develop a project which can run an executable on a remote computer. While that sounds similar to psexec
, I'd like it to just use the CPU & RAM of the remote computer. For everything else (registry, files, network, even access to devices through a driver), I'd like the request to be intercepted and sent back to the origin computer. The origin computer would process the request, then send the response back to be injected into the remote exe. I understand this would mean that I/O is slow, but the processes I have in mind are CPU & RAM intensive - so I'm happy to make that tradeoff.
This way I could farm out processes to other machines seamlessly, using their processing power but using local state.
Do you think Windows provides enough abstracted interfaces (through Detours and other mechanisms) to achieve a wrapper like that?
Thanks!
Fidel