Google Chrootme
I wonder what may explain Google Chrome behaves like a rootkit. Why on Earth a web browser need to mess-up with NtOpenProcessToken, NtOpenThreadTokenEx and stuff like that?
Reddit this / Add to del.icio.us / Digg this!I wonder what may explain Google Chrome behaves like a rootkit. Why on Earth a web browser need to mess-up with NtOpenProcessToken, NtOpenThreadTokenEx and stuff like that?
Reddit this / Add to del.icio.us / Digg this!More probaly to defend itself from banking trojans.
Most of these inject Parts of there own code into the browser to hijack data. This can be avoided by hooking these
Google Chrome runs in multiple processes. If I understand it correctly, it has a main process and then each tab in the browser is running in a seperate process. This means there needs to be some IPC mechanisms setup between the processes. This is probably why it is touching some Kernel APIs.