update README

Author: wiseaidev

README.md

@@ -70,7 +70,7 @@ To use the notebooks in this repository, you need to set up your environment. Fo
 | 2  | **Hidden Threads: Mastering the Art of Steganography in Rust** | 29 |  - Exploring the PNG File Format <br>- Reading amd Validating PNG Image Files <br>- Preprocessing PNG Images. <br>- Hiding Secrets with Steganography<br> | [![Github](https://img.shields.io/badge/launch-Github-181717.svg?logo=github&logoColor=white)](./chapter-2/chapter-2.ipynb) | [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/wiseaidev/dark-web-rust/main?filepath=chapter-2/chapter-2.ipynb) | [![nbviewer](https://img.shields.io/badge/Read%20PDF-nbviewer-blue)](https://nbviewer.org/github/wiseaidev/dark-web-rust/tree/main/chapter-2/chapter-2.pdf) |
 | 3  | **Rust's Cryptographic Strengths and Vulnerabilities** | 23 |  - Cryptography in Rust <br>- Hashing <br>- Cracking MD5 Hashes<br> - Implementing bcrypt<br> - Message Authentication<br> - Symmetric Encryption<br>  - Asymmetric Encryption<br>| [![Github](https://img.shields.io/badge/launch-Github-181717.svg?logo=github&logoColor=white)](./chapter-3/chapter-3.ipynb) | [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/wiseaidev/dark-web-rust/main?filepath=chapter-3/chapter-3.ipynb) | [![nbviewer](https://img.shields.io/badge/Read%20PDF-nbviewer-blue)](https://nbviewer.org/github/wiseaidev/dark-web-rust/tree/main/chapter-3/chapter-3.pdf) |
 | 4  | **Web Reconnaissance in Rust** | 26 |  - Web Reconnaissance and Social Engineering.<br>- Cookies management for persistent sessions.<br>- Crafting stealthy requests with custom user-agents.<br>- Leveraging proxies using Reqwest for enhanced security.<br>- Building a modular browser struct in Rust.<br>- Utilizing DuckDuckGo API for information gathering.<br>- Advanced interactions like image search and custom queries.<br>- Parsing Xeets in Rust for efficient data handling.<br>- Implementing anonymous email communication.<br>Mass social engineering techniques.| [![Github](https://img.shields.io/badge/launch-Github-181717.svg?logo=github&logoColor=white)](./chapter-4/chapter-4.ipynb) | [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/wiseaidev/dark-web-rust/main?filepath=chapter-4/chapter-4.ipynb) | [![nbviewer](https://img.shields.io/badge/Read%20PDF-nbviewer-blue)](https://nbviewer.org/github/wiseaidev/dark-web-rust/tree/main/chapter-4/chapter-4.pdf) |
-| 5  | **The Dirty COW vulnerability in Rust?** | TODO | TODO | TODO | TODO | TODO |
+| 5  | **The Dirty COW vulnerability in Rust** | 29 |  - Memory Mapping.<br>- Applications of Memory Mapping.<br>- Memory-Mapped Database.<br>- Memory-Mapped Networking.<br>- Shared and Private Memory Mapping.<br>- Copy On Write (COW) Mechanism.<br>- Madvise System Call and Read-Only Files.| [![Github](https://img.shields.io/badge/launch-Github-181717.svg?logo=github&logoColor=white)](./chapter-5/chapter-5.ipynb) | [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/wiseaidev/dark-web-rust/main?filepath=chapter-5/chapter-5.ipynb) | [![nbviewer](https://img.shields.io/badge/Read%20PDF-nbviewer-blue)](https://nbviewer.org/github/wiseaidev/dark-web-rust/tree/main/chapter-5/chapter-5.pdf) |
 
 ## 📜 License
 

chapter-5/README.md

@@ -613,7 +613,7 @@ Consider a scenario where two processes work in collaborative data processing by
 
 In contrast to shared mapping, the [**`MAP_PRIVATE`**](https://docs.rs/libc/latest/libc/constant.MAP_PRIVATE.html) option delves into the realm of data isolation and process-specific modifications. When a file is mapped using `MAP_PRIVATE`, the content becomes exclusive to the calling process's virtual memory. Any changes made to this memory are confined to the process itself, remaining invisible to other processes. Moreover, these changes do not permeate back to the underlying file, establishing a clear boundary between the private copy held in memory and the original file on disk.
 
-The `MAP_PRIVATE` option finds its utility when a process seeks an insulated workspace, free from external interference. In the realm of data privacy and security, this option ensures that modifications made within the mapped memory do not inadvertently affect other processes or the original file. Visualizing this in Figure 8.1 (b), a process utilizing `MAP_PRIVATE` creates a private copy of the file in its virtual memory, illustrating the encapsulation of changes within the confines of the individual process.
+The `MAP_PRIVATE` option finds its utility when a process seeks an insulated workspace, free from external interference. In the realm of data privacy and security, this option ensures that modifications made within the mapped memory do not inadvertently affect other processes or the original file.
 
 ```sh
                 +-----------------------------------+

chapter-5/chapter-5.ipynb

@@ -751,7 +751,7 @@
     "\n",
     "In contrast to shared mapping, the [**`MAP_PRIVATE`**](https://docs.rs/libc/latest/libc/constant.MAP_PRIVATE.html) option delves into the realm of data isolation and process-specific modifications. When a file is mapped using `MAP_PRIVATE`, the content becomes exclusive to the calling process's virtual memory. Any changes made to this memory are confined to the process itself, remaining invisible to other processes. Moreover, these changes do not permeate back to the underlying file, establishing a clear boundary between the private copy held in memory and the original file on disk.\n",
     "\n",
-    "The `MAP_PRIVATE` option finds its utility when a process seeks an insulated workspace, free from external interference. In the realm of data privacy and security, this option ensures that modifications made within the mapped memory do not inadvertently affect other processes or the original file. Visualizing this in Figure 8.1 (b), a process utilizing `MAP_PRIVATE` creates a private copy of the file in its virtual memory, illustrating the encapsulation of changes within the confines of the individual process.\n",
+    "The `MAP_PRIVATE` option finds its utility when a process seeks an insulated workspace, free from external interference. In the realm of data privacy and security, this option ensures that modifications made within the mapped memory do not inadvertently affect other processes or the original file.\n",
     "\n",
     "```sh\n",
     "                +-----------------------------------+\n",