lab5: Add link to the lab 5 archive

Add links to the lab archive and change directory references.

Signed-off-by: Stefan Jumarea <[email protected]>

Author: StefanJum

chapters/data/memory-security/drills/tasks/aslr/README.md

@@ -1,6 +1,6 @@
 # ASLR
 
-Navigate to `chapters/data/memory-security/drills/tasks/aslr` and run `make skels` to generate the `support/` folder.
+Navigate to the `aslr` directory in the lab archive (or `chapters/data/memory-security/drills/tasks/aslr` if you are working directly in the repository) and run `make skels` to generate the `support/` folder.
 Then navigate to `support/src`.
 
 Use the `Makefile.aslr` file to compile the `chapters/data/memory-security/drills/tasks/aslr/support/aslr.c` file:

chapters/data/memory-security/drills/tasks/bypassing-stack-protector/README.md

@@ -1,9 +1,9 @@
 # Bypassing the Stack Protector
 
-Navigate to `chapters/data/memory-security/drills/tasks/bypassing-stack-protector` and run `make skels` to generate the `support/` folder.
+Navigate to the `bypassing-stack-protector` directory in the lab archive (or `chapters/data/memory-security/drills/tasks/bypassing-stack-protector` if you are working directly in the repository) and run `make skels` to generate the `support/` folder.
 Then navigate to `support/src`.
 
-Inspect the `chapters/data/memory-security/drills/tasks/bypassing-stack-protector/support/stack_protector.c` source file.
+Inspect the `bypassing-stack-protector/support/stack_protector.c` source file.
 Compile the program and examine the object code.
 Try to identify the canary value.
 Using the `addr` variable, write 2 instructions: one that indexes `addr` to overwrite the canary with the correct value and one that indexes `addr` to overwrite the return address with the address of function `pawned()`.

chapters/data/memory-security/drills/tasks/exec-shellcode/README.md

@@ -1,11 +1,9 @@
 ## Shellcode Executor
 
-Navigate to `chapters/data/memory-security/drills/tasks/exec-shellcode` and run `make skels` to generate the `support/` folder.
+Navigate to the `exec-shellcode` directory in the lab archive (or `chapters/data/memory-security/drills/tasks/exec-shellcode` if you are working directly in the repository) and run `make skels` to generate the `support/` folder.
 Then navigate to `support/src`.
 
-Navigate to the `chapters/data/memory-security/drills/tasks/exec-shellcode/support/` directory.
-
-Your goal is to update the `src/exec-shellcode.s` source code file to be able to read and execute shellcodes from a given binary files.
+Your goal is to update the `exec-shellcode.s` source code file to be able to read and execute shellcodes from a given binary files.
 The program thus acts as a shellcode tester.
 
 A [shellcode](https://cocomelonc.github.io/tutorial/2021/10/09/linux-shellcoding-1.html) is a small program that is commonly used in memory-related security exploits as a form of arbitrary code execution.

chapters/data/memory-security/drills/tasks/pointer-arithmetic-leak/README.md

@@ -1,9 +1,8 @@
 # Wild Pointer Arithmetic Info Leak
 
-Navigate to `chapters/data/memory-security/drills/tasks/pointer-arithmetic-leak` and run `make skels` to generate the `support/` folder.
+Navigate to the `pointer-arithmetic-leak/` in the lab archive (or `chapters/data/memory-security/drills/tasks/pointer-arithmetic-leak` if you are working directly in the repository) and run `make skels` to generate the `support/` folder.
 Then navigate to `support/src`.
 
-Navigate to the `chapters/data/memory-security/drills/tasks/pointer-arithmetic-leak/support/` directory.
 Open and analyze the `buff_leak.c` file.
 
 The pointer `p` points to the stack.

chapters/data/memory-security/drills/tasks/stack-protector/README.md

@@ -1,9 +1,9 @@
 # Stack Protector
 
-Navigate to `chapters/data/memory-security/drills/tasks/stack-protector` and run `make skels` to generate the `support/` folder.
+Navigate to `stack-protector/` directory in the lab archive (or `chapters/data/memory-security/drills/tasks/stack-protector` if you are working directly in the repository) and run `make skels` to generate the `support/` folder.
 Then navigate to `support/src`.
 
-Comment the `-fno-stack-protector` switch from the `chapters/data/memory-security/drills/tasks/stack-protector/support/Makefile`, recompile and run the `bo_practice_write` executable.
+Comment the `-fno-stack-protector` switch from `stack-protector/support/Makefile`, recompile and run the `bo_practice_write` executable.
 Examine the binary with `objdump` and identify the instructions that set and test the canary.
 Observe what happens when a buffer overflow occurs.
 

chapters/data/overview/reading/lab5.md

@@ -0,0 +1 @@
+The contents of the lab are located in the [lab archive](https://github.com/cs-pub-ro/operating-systems/raw/refs/heads/lab-archives/Lab_5_Memory_Security.zip) and in the [GitHub repository](https://github.com/cs-pub-ro/operating-systems).

config.yaml

@@ -70,6 +70,7 @@ lab_structure:
   - title: Lab 5 - Memory Security
     filename: lab5.md
     content:
+      - reading/lab5.md
       - tasks/pointer-arithmetic-leak.md
       - tasks/aslr.md
       - tasks/stack-protector.md