You are viewing a single comment's thread.

view the rest of the comments →

[–] 26557191? 1 point -1 points (+0|-1) ago  (edited ago)

honestly, go fuck yourself, I was writing code on the Z80 before your Dad was a sperm

if you don't know how to overwrite malicious code on purpose, by using code from legit subroutines to overwrite the space it's sitting in, then it's YOU that doesn't know what they are talking about

[–] 26557338? ago  (edited ago)

That would mean you're likely younger than me you jackass, I started on a mainframe.

If you simply overwrite code with junk then you will trigger an error when that location is reached again. If its not gonna be reached then it would still be better to use nop/null or fake code as opposed to stack data because using stack data would look weird.

If you were to " overflow" the "biden function" that means you wrote more data than the size of it and were deleting other unrelated code or data as well.

In short you're just throwing around terms you vaguely remember without actually understanding them.

[–] 26557687? ago  (edited ago)

OK, same background, fair enough.

this is not understanding the other view on the problem I think.

.

.

drop malicious code somewhere into stack area

run code

"biden + 10,000"

set stack pointer back to start of malicious code

jump back to normal routines

malicious code eventually gets overwritten by normal usage

.

.

I don't know why this is a big deal for you, there is a billion+1 ways to inject untraceable code if you own the system