Thanks to contributors

nixawk · Dec 27, 2016 · 373cb04 · 373cb04
1 parent a85595a
commit 373cb04
Show file tree

Hide file tree

Showing 7 changed files with 23 additions and 0 deletions.
diff --git a/1.Information-Gathering/README.md b/1.Information-Gathering/README.md
@@ -1,3 +1,7 @@
+**Authors**: < [nixawk](https://github.com/nixawk) >, < [sjas](https://github.com/sjas) >
+
+----
+
 # Information Gathering
 
 In the *information gathering* phase, you will gather any information you can about the organization you are attacking by using social-media networks, Google hacking, footprinting the target, and so on. One of the most important skills a penetration tester can have is the ability to learn about a target, including how it behaves, how it operates, and how it ultimately can be attacked. The information that you gather about your target will give you valuable insight into the types of security controls in place.

diff --git a/1.Information-Gathering/Windows/README.md b/1.Information-Gathering/Windows/README.md
@@ -1,3 +1,6 @@
+**Authors**: < [nixawk](https://github.com/nixawk) >, < [patitoaxel](https://github.com/patitoaxel) >
+
+----
 
 # Information Gathering - Windows
 

diff --git a/2.Vulnerability-Assessment/README.md b/2.Vulnerability-Assessment/README.md
@@ -1,3 +1,6 @@
+**Authors**: < [nixawk](https://github.com/nixawk) >, < [sjas](https://github.com/sjas) >
+
+----
 
 # Vulnerability Assessment
 

diff --git a/3.Exploitation-Tools/README.md b/3.Exploitation-Tools/README.md
@@ -1,3 +1,7 @@
+**Authors**: < [nixawk](https://github.com/nixawk) >, < [binarymist](https://github.com/binarymist) >, < [bkimminich](https://github.com/bkimminich) >
+
+----
+
 # Exploitation Tools
 
 `Exploitation` is probably one of the most glamorous parts of a penetration test, yet it is often done with brute force rather than with precision. An exploit should be performed only when you know almost beyond a shadow of a doubt that a particular exploit will be successful. Of course, unforeseen protective measures might be in place on the target that prevent a particular exploit from working—but before you trigger a vulnerability, you should know that the system is vulnerable. Blindly firing off a mass onslaught of exploits and praying for a shell isn’t productive; it is noisy and provides little if any value to you as a penetration tester or to your client. Do your homework first, and then launch well-researched exploits that are likely to succeed.

diff --git a/7.Reporting/README.md b/7.Reporting/README.md
@@ -1,3 +1,6 @@
+**Authors**: < [nixawk](https://github.com/nixawk) >, < [sjas](https://github.com/sjas) >
+
+----
 
 # Reporting
 

diff --git a/CTFS/README.md b/CTFS/README.md
@@ -1,3 +1,6 @@
+**Authors**: < [nixawk](https://github.com/nixawk) >, < [sjas](https://github.com/sjas) >
+
+----
 
 # CTFS & PentestLab
 

diff --git a/README.md b/README.md
@@ -1,3 +1,6 @@
+**Authors**: < [nixawk](https://github.com/nixawk) >, < [m1guelpf](https://github.com/m1guelpf) >, < [binarymist](https://github.com/binarymist) >
+
+----
 
 # PENTEST-WIKI