How Does A Hack Actually Work?

>>58748527
You put the target system in a state that was not anticipated by its creator.

>>58748527
You eat with four chopsticks I think
Or five

>>58748527
https://en.wikipedia.org/wiki/Buffer_overflow
here you go read the whole page

File: Screen Shot 2017-02-01 at 13.02.27.png (43KB, 1158x62px) Image search: [Google]

43KB, 1158x62px

>>58748573

C/C++ btfo?

>>58748726
That's also what makes them so fast and efficient.

>>58748726
Okay, I'll bite.

Anyone who knows anything about C/C++ knows manual memory management (which enables buffer overflows) is a double-edged sword, and it's where the power of the language comes from. Being able to manipulate memory manually can reap enormous performance benefits, but in incompetent hands, it's disastrous. Even in large, mission critical open source projects that thousands of programmers have contributed towards, it's possible to miss a buffer overflow that tears a piece of software a new one; for example, Heartbleed.

>>58748726
>Bounds checking can prevent buffer overflows, but requires additional code and processing time

It literally requires a one line if statement, while the languages with built-in protection require a metric fuckton of layered libraries and overhead to do the same thing.

File: 1473575868748.png (152KB, 500x500px) Image search: [Google]

152KB, 500x500px

>>58748527
>How Does A Hack Actually Work?

>>58749029
What's your hourly rate, programmer who never makes mistakes and writes 100% flawless code?

File: 1484456188803.png (279KB, 500x500px) Image search: [Google]

279KB, 500x500px

>>58748527
>My understanding of hacks cones largely from Mr. Robot and other tech-based shows/films.