Attaching & Reading Process Memory from Kernel #shorts

What what do you think I have that? So what it's going to do first attach is going to allow me to attach a process and then move the process memory from that target process into my target process into the process. Um so that's attach then read memory is going to allow me to read the memory of attacked process. Write memory is almost the same implementation but the other way around. I'm going to be able to write memory from the kernel. Check writable is basically going to try to write something in the memory of that process of that user memory process and if it doesn't is it doesn't succeed the statute is is is not the good status. So

basically zero then uh it means that you cannot write it into it. So that's why you have to do check writable then kill process and choose killing a process. Yeah from target from from my P ID. So finding the the process P ID and then choose calling from the kernel U is a different function is set W terminate process. So why is different? Why is important? Because the kernel is higher high on the hierarchy of of processes. So you can kill anything from the from the from the kernel. Same from read and write memory. You might hear about ppl process proc protected process light like uh the antiviruses. They run with ppl uh they run with uh with system

rightes. Uh same for edrs. You cannot interact with them. You cannot read the memory of them and you cannot uh you can not directly you cannot access the handles for example to the antimalware uh from uh Microsoft right so MSMP you cannot choose you cannot read the handle of it. If you are kernel you can right. Right.