docs(cybersecurity): add warning to advise that projects are for educative purposes only

subjects/cybersecurity/README.md

@@ -1,26 +0,0 @@
-# :shield: IT Security
-
-:warning: | **In compliance with the laws.**
-
-_The methods and tools cited in these courses are used for educational and preventive purposes only, and for private use._
-
-_The necessary precautions have been put in place to ensure legal learning without risk to others._
-
-_It is your responsibility to check the laws applicable in your country and the rules in force._
-
-_By integrating this program, you thus declare yourself solely responsible for your actions, and no responsibility on the part of 01 or the instructor will be engaged for the misuse of the content._
-
----
-
-By downloading or consulting this document, the user accepts the user license attached to it, as detailed in the following provisions, and undertakes to fully respect it.
-
-The right of use defined by the license is limited to use in an exclusively private setting. This right includes:
-
-- The right to reproduce the document for storage for the purpose of representation on a single computer terminal
-- The right to reproduce the document in one copy for backup or printing
-
-No modification of the document in its content, form or presentation nor any redistribution in whole or in part, in any form and medium whatsoever (and in particular by networking) are authorized.
-
-The statements relating to the source of the document and-or its author must be kept in their entirety.
-
-The right of use defined by the license is personal and non-exclusive. Any other use than those provided for by the license is subject to the prior authorization of the author.

subjects/cybersecurity/active/README.md

@@ -42,3 +42,5 @@ Files that must be inside your repository:
 - a README.md file, Which clearly explains how to use the program.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/evasion/README.md

@@ -25,4 +25,6 @@ Files that must be inside your  repository:
 - Your program source code.
 - a README.md file, Which clearly explains how to use the program.
 
-Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/hole-in-bin/README.md

@@ -22,3 +22,5 @@ Files that must be inside your repository:
 - a README.md file, Which explains all the steps you went through in order to bypass the program.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/injector/README.md

@@ -39,3 +39,5 @@ Files that must be inside your repository:
 - a README.md file, Which clearly explains how to use the program.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/inspector-image/README.md

@@ -77,3 +77,5 @@ Files that must be inside your repository:
 - a README.md file, Which clearly explains how to use the program.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/local/README.md

@@ -25,3 +25,5 @@ Files that must be inside your repository:
 - a README.md file, Which explains all the steps you went through in order to reach root access.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/mal-track/README.md

@@ -24,4 +24,6 @@ Files that must be inside your  repository:
 - Your program source code.
 - a README.md file, Which clearly explains how to use the program.
 
-- Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+- Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/malware/README.md

@@ -35,3 +35,5 @@ Files that must be inside your repository:
 - a README.md file, Which clearly explains how to use the program.
 
 - Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/obfuscator/README.md

@@ -22,3 +22,5 @@ Files that must be inside your repository:
 - a README.md file, Which clearly explains how to use the program.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/passive/README.md

@@ -76,3 +76,5 @@ Files that must be inside your repository:
 - a README.md file, Which clearly explains how to use the program.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.

subjects/cybersecurity/web-hack/README.md

@@ -16,3 +16,5 @@ Files that must be inside your repository:
 - a README.md file, Which explains all the steps you went through in order to benefit from the all vulnerabilities and how to fix all of them.
 
 Don’t hesitate to double check the names of your folders and files to ensure they are correct!
+
+> ⚠️ These methods and tools are for educational purposes only, so that you have a better understanding of how to protect against similar vulnerabilities. You must ensure that you do not attempt any exploit-type activity without the explicit permission of the owner of the machine, system or application. Failure to obtain permission risks breaking the law.