>be 22yr old fat kv NEET
>always had an interest in programming and tech in general
>learn C, socket programming, programming microcontrollers by watching YouTube videos or reading up PDFs
>family tells me I should join an ethical hacking course and get a job on the basis of that
>not a bad idea.jpg
>join course
>it's all about a tiny bit of theory and using tools like metasploit, and nmap
>not one line of programming
>I was expecting to learn raw socket programming and analyzing source code to find vulnerabilities
What is this tomfoolery
>>53641243
read this OP http://beej.us/guide/bgnet/
pic related
Most "hacking" is just poor configuration - you don't need to look through source code or write a special exploit, just spot a well-known vulnerability and you're at home.
>>53641243
>white hat hacking (aka cracking)
>analysing source code (aka software cracking)
You dun goof'd.
>>53641275
That's exactly where I learned socket programming, great book
>>53641243
If you don't put much into it, most schools are expensive daycares that give you a piece of paper for employers. Take advantage of the resources your school offers. Pick your professors brains at least.
>he fell for the school meme
>not making your own way as a hacker vigilante
>>53641282
>you don't need to look through source code or write a special exploit, just spot a well-known vulnerability
how do you spot a vulnerability without the source code
I always thought most hackers decompiled a program in order to learn how it works, then create a patch to bypass whatever it is they want.
Honestly I'd love to learn how to create my own clean software patches.
>>53641282
This. However being able to find exploits in software pays a hell of a lot more (and it's actually legal to do).
I'm pretty sure there are resources that will teach you the most common programming mistakes to find (buffer overflows etc), but beyond that, it's pretty challenging.
Detecting obscure and minor errors in source code or machine code is not a very standardized procedure AFAIK.
You're learning the basics of finding exploits.
How to buffer overflow/underflow, replay packets, etc.
Once you're familiar with that stage, then you should study why the exploit works by looking at the source code.
