Reply to thread

Message

<blockquote data-quote="436880927" data-source="post: 828130">[USER=32260]@Andy Ful[/USER] I recon that you already understand what I have been saying.Sure, I think MemProtect is crap, but all of that is irrelevant.All of this started because I mentioned that MemProtect cannot stop others running at the same privilege level - kernel-mode. And I am right.Sure, there are ways to inject code into another process in user-mode without triggering MemProtect... but it is out of scope to MemProtect because of the design that MemProtect uses. What about targeting shared memory? Yeah, it doesn&#039;t cover that one either. Oops!Generally speaking, MemProtect will work in the real-world. For now.There doesn&#039;t need to be aggro, but I am not the bad guy here. I shouldn&#039;t have to explain the same things over and over. It isn&#039;t my fault that die hard fans aren&#039;t willing to accept simple truths.If people do not understand the &quot;techno talk&quot; then don&#039;t get involved with the discussions. You don&#039;t tell people they are wrong when you don&#039;t understand them. You educate yourself and return when you understand or stop.This discussion has turned absolutely bizzarre... and I have gone lightly on people in this thread. On the technical forums - or just go for the Russian ones on the deep web - people get smashed for asking simple questions: now that is rudeness.Anyway, I will leave it as follows:1. People at the same privilege level as you can beat you.2. AVs can inject code into Google Chrome and there is nothing Google can do to indefinitely stop it. This is why they went for the warnings and failed to do what they claimed they would starting with the beginning of 2019.3. There is more to injecting code than DLL injection. No DLL is required. 4. MemProtect does not explicitly prevent code injection. Problem solved if people who do not understand stop quoting me with nonsense.</blockquote>

[QUOTE="436880927, post: 828130"] [USER=32260]@Andy Ful[/USER] I recon that you already understand what I have been saying. Sure, I think MemProtect is crap, but all of that is irrelevant. All of this started because I mentioned that MemProtect cannot stop others running at the same privilege level - kernel-mode. And I am right. Sure, there are ways to inject code into another process in user-mode without triggering MemProtect... but it is out of scope to MemProtect because of the design that MemProtect uses. What about targeting shared memory? Yeah, it doesn't cover that one either. Oops! Generally speaking, MemProtect will work in the real-world. For now. There doesn't need to be aggro, but I am not the bad guy here. I shouldn't have to explain the same things over and over. It isn't my fault that die hard fans aren't willing to accept simple truths. If people do not understand the "techno talk" then don't get involved with the discussions. You don't tell people they are wrong when you don't understand them. You educate yourself and return when you understand or stop. This discussion has turned absolutely bizzarre... and I have gone lightly on people in this thread. On the technical forums - or just go for the Russian ones on the deep web - people get smashed for asking simple questions: now that is rudeness. Anyway, I will leave it as follows: 1. People at the same privilege level as you can beat you. 2. AVs can inject code into Google Chrome and there is nothing Google can do to indefinitely stop it. This is why they went for the warnings and failed to do what they claimed they would starting with the beginning of 2019. 3. There is more to injecting code than DLL injection. No DLL is required. 4. MemProtect does not explicitly prevent code injection. Problem solved if people who do not understand stop quoting me with nonsense. [/QUOTE]

Verification