+- Sinisterly (https://sinister.li)
+-- Forum: Hacking (https://sinister.li/Forum-Hacking)
+--- Forum: Tutorials (https://sinister.li/Forum-Tutorials)
+--- Thread: Tutorial How to start Hacking. Part 1. (/Thread-Tutorial-How-to-start-Hacking-Part-1)
RE: How to start Hacking. Part 1. - DarkMuse - 06-27-2014
If I may interject for a second. I feel like @superMAUS could make a really good basic tutorial on how to hack but this stuff is not basic at all. I'm lost xD
RE: How to start Hacking. Part 1. - superMAUS - 06-28-2014
(06-27-2014, 02:24 PM)DarkMuse Wrote: If I may interject for a second. I feel like @superMAUS could make a really good basic tutorial on how to hack but this stuff is not basic at all. I'm lost xD
Haha, all in good time.
Re: RE: How to start Hacking. Part 1. - DarkMuse - 06-28-2014
(06-28-2014, 12:37 AM)superMAUS Wrote: Haha, all in good time.Then I shall wait ^.^
RE: How to start Hacking. Part 1. - Dyme - 06-28-2014
This is really vulnerability discovery in an open source project more than anything, and teaching someone how to use grep and cat really doesn't cut it. It's just gonna be the same old shit that join7seven made a tutorial on in which he audited some shitty php code that had a sqli vulnerability so obvious that vehla could find it.
Here let me save you the work:
http://www.hackforums.net/showthread.php?tid=3116315
http://www.hackforums.net/showthread.php?tid=3108156
And if you are gonna argue "but dim I was gonna audit C becuz memory corruption vulns r leet af", it's the same shit. Grep for insecure functions and see what the code does with input that can be provided via the user. Idk if a concept as rudimentary as that requires a multipart tutorial.
(06-25-2014, 09:53 AM)BreShiE Wrote: Wow, one of the few that doesn't say learn SQLi and XSS. Nice post OP, hope to see more from you.
One would think you need to understand SQLi and XSS vulnerabilities if you're going to be auditing code to find them...
RE: How to start Hacking. Part 1. - Alan Turing - 06-28-2014
(06-28-2014, 06:26 PM)Dyme Wrote: This is really vulnerability discovery in an open source project more than anything, and teaching someone how to use grep and cat really doesn't cut it. It's just gonna be the same old shit that join7seven made a tutorial on in which he audited some shitty php code that had a sqli vulnerability so obvious that vehla could find it.
Here let me save you the work:
http://www.hackforums.net/showthread.php?tid=3116315
http://www.hackforums.net/showthread.php?tid=3108156
And if you are gonna argue "but dim I was gonna audit C becuz memory corruption vulns r leet af", it's the same shit. Grep for insecure functions and see what the code does with input that can be provided via the user. Idk if a concept as rudimentary as that requires a multipart tutorial.
One would think you need to understand SQLi and XSS vulnerabilities if you're going to be auditing code to find them...
hey hey joinseventh is a good guy
RE: How to start Hacking. Part 1. - misnar - 07-01-2014
(06-28-2014, 06:26 PM)Dyme Wrote: This is really vulnerability discovery in an open source project more than anything, and teaching someone how to use grep and cat really doesn't cut it. It's just gonna be the same old shit that join7seven made a tutorial on in which he audited some shitty php code that had a sqli vulnerability so obvious that vehla could find it.
Here let me save you the work:
http://www.hackforums.net/showthread.php?tid=3116315
http://www.hackforums.net/showthread.php?tid=3108156
And if you are gonna argue "but dim I was gonna audit C becuz memory corruption vulns r leet af", it's the same shit. Grep for insecure functions and see what the code does with input that can be provided via the user. Idk if a concept as rudimentary as that requires a multipart tutorial.
One would think you need to understand SQLi and XSS vulnerabilities if you're going to be auditing code to find them...
see: https://www.sinister.ly/Thread-Tutorial-How-to-Use-Cat
Quote:"but dim I was gonna audit C becuz memory corruption vulns r leet af"
implying anyone here has more than a basic understanding of a buffer overflow