because if you write code that has no bugs in it whatsoever, then it cannot be exploited.
You're claiming that every piece of code ever written can be exploited (Within a reasonable amount of time) to the point of being 100% insecure.You see, that's incorrect because if you write code that has no bugs in it whatsoever, then it cannot be exploited. And guess what? That's 100% possible.
Bugs can't always be found until they are tested, and I have never heard of any code that cannot be twisted or exploited in any way.
echo("Hello!");
A key.dat file, by itself, is useless to 'hackers.' Only when you have a second key.dat file generated on the same computer with a key you know can you extract the key from the first key.dat. I explained the process here.The issue is that CBMHost is not a secure or professional hosting service. Any legitimate hosting service would use FTP jailing AND access restrictions to prevent users from accessing other users' key.dat files. They'd also (hopefully) use secure passwords on administrator accounts. None of the people involved in this are known for RATing, so I highly doubt that a keylogger or other tool of its kind was used to break in. It was negligence on behalf of CBMHost that left some kind of access violation open for exploitation.
My server was hacked and exploited with a directory traversal attack according to my source.
Code: [Select]echo("Hello!");
What if a byte of code is corrupted due to a glitch in the system caused by an attack (And this scenario is pretty stretched I know, but it can still happen).
unless you count cosmic rays flipping bits in ram an attack.
What if a byte of code is corrupted due to a glitch in the system caused by an attack (And this scenario is pretty stretched I know, but it can still happen). It can say something else as the system tries to find the bytes to display each letter.
depends on what you want to exploit in that code. If my goal was to exploit that to say another message than I guess I exploited it.
