12-05-2024, 07:41 AM
- Network connections to the remote proxy server (the proxy client) is
handled by two other instances of itself, instead of just the main instance.
So, there'll be 3 "u.exe" processes. There should be no reason to spawn
another instances of itself to do other tasks unless they're frequently
crash.
- This one is a surprise. The main instance of the application always tries
to download "u.exe" file when the application starts, and use that to spawn
the proxy client processes, instead of existing one which is already in the
computer. Turns out that the downloaded "u.exe" file is actually different
than the "u.exe" of the main application. This different "u.exe" can be used
to efficiently spy users, since it always get updated.
Source:
https://groups.google.com/g/microsoft.pu...CgAJ?pli=1
handled by two other instances of itself, instead of just the main instance.
So, there'll be 3 "u.exe" processes. There should be no reason to spawn
another instances of itself to do other tasks unless they're frequently
crash.
- This one is a surprise. The main instance of the application always tries
to download "u.exe" file when the application starts, and use that to spawn
the proxy client processes, instead of existing one which is already in the
computer. Turns out that the downloaded "u.exe" file is actually different
than the "u.exe" of the main application. This different "u.exe" can be used
to efficiently spy users, since it always get updated.
Source:
https://groups.google.com/g/microsoft.pu...CgAJ?pli=1