From 6a8eb855d4c8e670b455765c961a031d8e39b9b8 Mon Sep 17 00:00:00 2001 From: Razvan Date: Sat, 25 Apr 2026 12:19:50 +0300 Subject: [PATCH] labs: Fix console and link formatting in README files Standardize the formatting for console output and reading material links across multiple lab tasks to ensure consistency and fix CI checkpatch failures. Signed-off-by: Razvan --- labs/lab-01/tasks/len-xor/README.md | 2 +- labs/lab-01/tasks/mirror/README.md | 2 +- labs/lab-01/tasks/odd-even/README.md | 2 +- labs/lab-01/tasks/rotations/README.md | 2 +- labs/lab-02/tasks/delete_first/README.md | 2 +- labs/lab-02/tasks/find_max/README.md | 2 +- labs/lab-02/tasks/iterate/README.md | 2 +- labs/lab-02/tasks/pixels/README.md | 2 +- labs/lab-02/tasks/pointers/README.md | 2 +- labs/lab-03/tasks/binary_search/README.md | 2 +- labs/lab-03/tasks/vector_max/README.md | 2 +- labs/lab-04/tasks/cf-of/README.md | 2 +- labs/lab-04/tasks/conditional-jumps/README.md | 2 +- labs/lab-04/tasks/fibonacci/README.md | 2 +- labs/lab-04/tasks/grumpy-jumps/README.md | 2 +- labs/lab-04/tasks/min/README.md | 2 +- labs/lab-04/tasks/sets/README.md | 2 +- labs/lab-05/tasks/div/README.md | 2 +- labs/lab-05/tasks/mul/README.md | 2 +- labs/lab-05/tasks/sum-array/README.md | 2 +- labs/lab-05/tasks/sum-squared/README.md | 2 +- labs/lab-05/tasks/vec-count-if/README.md | 2 +- labs/lab-06/tasks/fibonacci/README.md | 2 +- labs/lab-06/tasks/find-substring/README.md | 2 +- labs/lab-06/tasks/getters-setters/README.md | 2 +- labs/lab-06/tasks/mul-arrays/README.md | 2 +- labs/lab-06/tasks/print-structure/README.md | 2 +- labs/lab-08/guides/disassembling-c/README.md | 2 +- labs/lab-08/tasks/print-rev-string/README.md | 6 +++--- labs/lab-08/tasks/rot13/README.md | 6 +++--- labs/lab-08/tasks/string-print-len/README.md | 6 +++--- labs/lab-08/tasks/string-print/README.md | 6 +++--- labs/lab-08/tasks/sum7/README.md | 6 +++--- labs/lab-08/tasks/to-upper/README.md | 6 +++--- labs/lab-10/tasks/overwrite-ret-addr/README.md | 4 ++-- labs/lab-10/tasks/overwrite-ret-addr/solution/README.md | 2 +- labs/lab-11/guides/cpp-obs/README.md | 4 ++-- labs/lab-11/tasks/entry-fix-1/README.md | 4 ++-- labs/lab-11/tasks/entry-fix-2/README.md | 4 ++-- labs/lab-11/tasks/export-fix/README.md | 4 ++-- labs/lab-11/tasks/include-fix/README.md | 4 ++-- labs/lab-11/tasks/lib-fix/README.md | 4 ++-- labs/lab-11/tasks/multiple-link/README.md | 4 ++-- labs/lab-11/tasks/obj-link-dev/README.md | 4 ++-- labs/lab-11/tasks/single-link/README.md | 4 ++-- labs/lab-11/tasks/var-func-fix/README.md | 4 ++-- labs/lab-11/tasks/vars-obs/README.md | 4 ++-- labs/lab-12/tasks/feeling-chained/README.md | 2 +- labs/lab-12/tasks/indirect-business/README.md | 2 +- labs/lab-12/tasks/rip-my-buffers-off/README.md | 2 +- labs/lab-12/tasks/rop/README.md | 2 +- 51 files changed, 75 insertions(+), 75 deletions(-) diff --git a/labs/lab-01/tasks/len-xor/README.md b/labs/lab-01/tasks/len-xor/README.md index 67f1e34e5..75656230f 100644 --- a/labs/lab-01/tasks/len-xor/README.md +++ b/labs/lab-01/tasks/len-xor/README.md @@ -44,7 +44,7 @@ Use pointer operations and bitwise operations as much as possible! To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/len-xor/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-01/tasks/mirror/README.md b/labs/lab-01/tasks/mirror/README.md index 891dcd552..9c40faa73 100644 --- a/labs/lab-01/tasks/mirror/README.md +++ b/labs/lab-01/tasks/mirror/README.md @@ -25,7 +25,7 @@ The `mirror` function should perform an **in-place** reversal of the characters To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/mirror/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-01/tasks/odd-even/README.md b/labs/lab-01/tasks/odd-even/README.md index 923e4a33e..57136a5f5 100644 --- a/labs/lab-01/tasks/odd-even/README.md +++ b/labs/lab-01/tasks/odd-even/README.md @@ -26,7 +26,7 @@ Traverse an array of 32-bit integers using pointer operations and display the ev To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/odd-even/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-01/tasks/rotations/README.md b/labs/lab-01/tasks/rotations/README.md index 04977cf09..1564b17c5 100644 --- a/labs/lab-01/tasks/rotations/README.md +++ b/labs/lab-01/tasks/rotations/README.md @@ -25,7 +25,7 @@ Implement left and right rotations for 32-bit integers in C. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/rotations/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-02/tasks/delete_first/README.md b/labs/lab-02/tasks/delete_first/README.md index bae1d4e4c..9a6b23723 100644 --- a/labs/lab-02/tasks/delete_first/README.md +++ b/labs/lab-02/tasks/delete_first/README.md @@ -21,7 +21,7 @@ Given a string and a pattern, implement the `delete_first(char *s, char *pattern To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/delete_first/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-02/tasks/find_max/README.md b/labs/lab-02/tasks/find_max/README.md index d05064d12..458cd02a3 100644 --- a/labs/lab-02/tasks/find_max/README.md +++ b/labs/lab-02/tasks/find_max/README.md @@ -22,7 +22,7 @@ compare(const void *a, const void *b) To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/find_max/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-02/tasks/iterate/README.md b/labs/lab-02/tasks/iterate/README.md index 13011fa55..29f69794e 100644 --- a/labs/lab-02/tasks/iterate/README.md +++ b/labs/lab-02/tasks/iterate/README.md @@ -37,7 +37,7 @@ Iterate through the addresses in `v` byte by byte, two bytes at a time, four byt To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/iterate/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-02/tasks/pixels/README.md b/labs/lab-02/tasks/pixels/README.md index 12448d6a2..dc98faec0 100644 --- a/labs/lab-02/tasks/pixels/README.md +++ b/labs/lab-02/tasks/pixels/README.md @@ -47,7 +47,7 @@ p.b = 0.11 * p.b; To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/pixels/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-02/tasks/pointers/README.md b/labs/lab-02/tasks/pointers/README.md index 7835e7b71..4ac5c24d3 100644 --- a/labs/lab-02/tasks/pointers/README.md +++ b/labs/lab-02/tasks/pointers/README.md @@ -12,7 +12,7 @@ Implement the functions [`memcpy()`](http://www.cplusplus.com/reference/cstring/ To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/pointers/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-03/tasks/binary_search/README.md b/labs/lab-03/tasks/binary_search/README.md index fdd6b364b..d1c6b9082 100644 --- a/labs/lab-03/tasks/binary_search/README.md +++ b/labs/lab-03/tasks/binary_search/README.md @@ -28,7 +28,7 @@ The skeleton for the code is in `binary_search/support/binary_search.c`. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/binary_search/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-03/tasks/vector_max/README.md b/labs/lab-03/tasks/vector_max/README.md index e6f88f35b..3eb2f97dd 100644 --- a/labs/lab-03/tasks/vector_max/README.md +++ b/labs/lab-03/tasks/vector_max/README.md @@ -28,7 +28,7 @@ The skeleton for the code is in `vector_max/support/vector_max.c`. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/vector_max/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-04/tasks/cf-of/README.md b/labs/lab-04/tasks/cf-of/README.md index 0cbfe122b..03cd930ba 100644 --- a/labs/lab-04/tasks/cf-of/README.md +++ b/labs/lab-04/tasks/cf-of/README.md @@ -18,7 +18,7 @@ Using the `add` instruction on the `al` register: To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/cf-of/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-04/tasks/conditional-jumps/README.md b/labs/lab-04/tasks/conditional-jumps/README.md index f508100d2..b6e37db75 100644 --- a/labs/lab-04/tasks/conditional-jumps/README.md +++ b/labs/lab-04/tasks/conditional-jumps/README.md @@ -31,7 +31,7 @@ Avoid infinite looping. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/conditional-jumps/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-04/tasks/fibonacci/README.md b/labs/lab-04/tasks/fibonacci/README.md index 29137feb7..4c688b2f5 100644 --- a/labs/lab-04/tasks/fibonacci/README.md +++ b/labs/lab-04/tasks/fibonacci/README.md @@ -18,7 +18,7 @@ Calculate the Nth Fibonacci number, where N is given through the `rcx` register. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/fibonacci/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-04/tasks/grumpy-jumps/README.md b/labs/lab-04/tasks/grumpy-jumps/README.md index 1495b4271..c3159d63e 100644 --- a/labs/lab-04/tasks/grumpy-jumps/README.md +++ b/labs/lab-04/tasks/grumpy-jumps/README.md @@ -18,7 +18,7 @@ Modify the source so that the wrong message is not displayed anymore. To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/grumpy-jumps/tests$ ./run_all_tests.sh test_display_right ........................ passed ... 50 test_display_only_right ........................ passed ... 50 diff --git a/labs/lab-04/tasks/min/README.md b/labs/lab-04/tasks/min/README.md index 8f9f8bf82..75bf64752 100644 --- a/labs/lab-04/tasks/min/README.md +++ b/labs/lab-04/tasks/min/README.md @@ -12,7 +12,7 @@ Calculate the minimum of the numbers in 2 registers (`r9` and `r10`) using a com To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/min/tests$ ./run_all_tests.sh test_use_compare ........................ passed ... 10 test_use_jump ........................ passed ... 10 diff --git a/labs/lab-04/tasks/sets/README.md b/labs/lab-04/tasks/sets/README.md index 3bd86ae94..73986183c 100644 --- a/labs/lab-04/tasks/sets/README.md +++ b/labs/lab-04/tasks/sets/README.md @@ -45,7 +45,7 @@ Perform the union of the two sets. To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/sets/tests$ ./run_all_tests.sh test_reunion ........................ passed ... 10 test_add_value_in_first_set ........................ passed ... 20 diff --git a/labs/lab-05/tasks/div/README.md b/labs/lab-05/tasks/div/README.md index 62c6fc8b6..653894b22 100644 --- a/labs/lab-05/tasks/div/README.md +++ b/labs/lab-05/tasks/div/README.md @@ -50,7 +50,7 @@ The divisor is passed as an argument to the `div` mnemonic. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/div/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-05/tasks/mul/README.md b/labs/lab-05/tasks/mul/README.md index b2e1b7cc2..4ec2f4835 100644 --- a/labs/lab-05/tasks/mul/README.md +++ b/labs/lab-05/tasks/mul/README.md @@ -66,7 +66,7 @@ You'll need to multiply: To test the implementation, enter the tests/ directory and run: ```console -make check +student@hsi:~/.../tasks/mul/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-05/tasks/sum-array/README.md b/labs/lab-05/tasks/sum-array/README.md index 776f78dcd..8a237122f 100644 --- a/labs/lab-05/tasks/sum-array/README.md +++ b/labs/lab-05/tasks/sum-array/README.md @@ -62,7 +62,7 @@ big_qword_array dq 9223372036854775800, 8223372036854775800, 7223372036854775800 To test the implementation, enter the tests/ directory and run: ```console -make check +student@hsi:~/.../tasks/sum-array/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-05/tasks/sum-squared/README.md b/labs/lab-05/tasks/sum-squared/README.md index 4fde19296..5a06b4424 100644 --- a/labs/lab-05/tasks/sum-squared/README.md +++ b/labs/lab-05/tasks/sum-squared/README.md @@ -30,7 +30,7 @@ Therefore, you cannot easily use the `rax` register to store the sum of squares. To test your implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/sum-squared/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-05/tasks/vec-count-if/README.md b/labs/lab-05/tasks/vec-count-if/README.md index 301354fc9..f5f8fd187 100644 --- a/labs/lab-05/tasks/vec-count-if/README.md +++ b/labs/lab-05/tasks/vec-count-if/README.md @@ -34,7 +34,7 @@ For negative numbers, sign extension should be performed; it would work without To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/vec-count-if/tests$ make check ``` In order to get the points, you should have a single line of output with diff --git a/labs/lab-06/tasks/fibonacci/README.md b/labs/lab-06/tasks/fibonacci/README.md index 81124fc35..09986e4f4 100644 --- a/labs/lab-06/tasks/fibonacci/README.md +++ b/labs/lab-06/tasks/fibonacci/README.md @@ -12,7 +12,7 @@ The sum of the first 9 numbers is 54. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/fibonacci/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-06/tasks/find-substring/README.md b/labs/lab-06/tasks/find-substring/README.md index 33575c77b..a10082055 100644 --- a/labs/lab-06/tasks/find-substring/README.md +++ b/labs/lab-06/tasks/find-substring/README.md @@ -26,7 +26,7 @@ Substring found at index: To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/find-substring/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-06/tasks/getters-setters/README.md b/labs/lab-06/tasks/getters-setters/README.md index 31318d6d9..f2114d78d 100644 --- a/labs/lab-06/tasks/getters-setters/README.md +++ b/labs/lab-06/tasks/getters-setters/README.md @@ -32,7 +32,7 @@ Follow the comments marked with **TODO**. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/getters-setters/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-06/tasks/mul-arrays/README.md b/labs/lab-06/tasks/mul-arrays/README.md index ee873438e..7db645950 100644 --- a/labs/lab-06/tasks/mul-arrays/README.md +++ b/labs/lab-06/tasks/mul-arrays/README.md @@ -24,7 +24,7 @@ Therefore, the result is stored on two bytes. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/mul-arrays/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-06/tasks/print-structure/README.md b/labs/lab-06/tasks/print-structure/README.md index 56fa10815..7d857967f 100644 --- a/labs/lab-06/tasks/print-structure/README.md +++ b/labs/lab-06/tasks/print-structure/README.md @@ -25,7 +25,7 @@ Do not modify the structure in the `.data` section, you need to use code to modi To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/print-structure/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-08/guides/disassembling-c/README.md b/labs/lab-08/guides/disassembling-c/README.md index ec0f718ca..a57c8bc00 100644 --- a/labs/lab-08/guides/disassembling-c/README.md +++ b/labs/lab-08/guides/disassembling-c/README.md @@ -67,7 +67,7 @@ where `` is the path to the object file `test.o`. Afterwards, you'll see an output similar to the following: ```console -$ objdump -M intel -d test.o +student@hsi:~/.../guides/disassembling-c/support$ objdump -M intel -d test.o test.o: file format elf64-x86-64 diff --git a/labs/lab-08/tasks/print-rev-string/README.md b/labs/lab-08/tasks/print-rev-string/README.md index ee635a74d..5fd2e704d 100644 --- a/labs/lab-08/tasks/print-rev-string/README.md +++ b/labs/lab-08/tasks/print-rev-string/README.md @@ -81,19 +81,19 @@ After you consider your implementation complete, it is recommended to first run In order to do so, enter the `support/` directory and run: ```console -make +student@hsi:~/.../tasks/print-rev-string/support$ make ``` If your code successfully compiled, you can then run the binary like so: ```console -./print_reverse_string +student@hsi:~/.../tasks/print-rev-string/support$ ./print_reverse_string ``` To fully test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/print-rev-string/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-08/tasks/rot13/README.md b/labs/lab-08/tasks/rot13/README.md index c8ebf6ef4..f01e1c31d 100644 --- a/labs/lab-08/tasks/rot13/README.md +++ b/labs/lab-08/tasks/rot13/README.md @@ -35,19 +35,19 @@ After you consider your implementation complete, it is recommended to first run In order to do so, enter the `support/` directory and run: ```console -make +student@hsi:~/.../tasks/rot13/support$ make ``` If your code successfully compiled, you can then run the binary like so: ```console -./rot13 +student@hsi:~/.../tasks/rot13/support$ ./rot13 ``` To fully test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/rot13/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-08/tasks/string-print-len/README.md b/labs/lab-08/tasks/string-print-len/README.md index e0f8708a3..c61d99c72 100644 --- a/labs/lab-08/tasks/string-print-len/README.md +++ b/labs/lab-08/tasks/string-print-len/README.md @@ -31,19 +31,19 @@ After you consider your implementation complete, it is recommended to first run In order to do so, enter the `support/` directory and run: ```console -make +student@hsi:~/.../tasks/string-print-len/support$ make ``` If your code successfully compiled, you can then run the binary like so: ```console -./print_string_length +student@hsi:~/.../tasks/string-print-len/support$ ./print_string_length ``` To fully test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/string-print-len/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-08/tasks/string-print/README.md b/labs/lab-08/tasks/string-print/README.md index 3d7e18082..53848353d 100644 --- a/labs/lab-08/tasks/string-print/README.md +++ b/labs/lab-08/tasks/string-print/README.md @@ -19,19 +19,19 @@ After you consider your implementation complete, it is recommended to first run In order to do so, enter the `support/` directory and run: ```console -make +student@hsi:~/.../tasks/string-print/support$ make ``` If your code successfully compiled, you can then run the binary like so: ```console -./print_string +student@hsi:~/.../tasks/string-print/support$ ./print_string ``` To fully test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/string-print/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-08/tasks/sum7/README.md b/labs/lab-08/tasks/sum7/README.md index c217517f2..3bbfd0703 100644 --- a/labs/lab-08/tasks/sum7/README.md +++ b/labs/lab-08/tasks/sum7/README.md @@ -17,19 +17,19 @@ After you consider your implementation complete, it is recommended to first run In order to do so, enter the `support/` directory and run: ```console -make +student@hsi:~/.../tasks/sum7/support$ make ``` If your code successfully compiled, you can then run the binary like so: ```console -./sum7 +student@hsi:~/.../tasks/sum7/support$ ./sum7 ``` To fully test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/sum7/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-08/tasks/to-upper/README.md b/labs/lab-08/tasks/to-upper/README.md index d9227f605..248dfe830 100644 --- a/labs/lab-08/tasks/to-upper/README.md +++ b/labs/lab-08/tasks/to-upper/README.md @@ -34,19 +34,19 @@ After you consider your implementation complete, it is recommended to first run In order to do so, enter the `support/` directory and run: ```console -make +student@hsi:~/.../tasks/to-upper/support$ make ``` If your code successfully compiled, you can then run the binary like so: ```console -./to_upper +student@hsi:~/.../tasks/to-upper/support$ ./to_upper ``` To fully test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/to-upper/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-10/tasks/overwrite-ret-addr/README.md b/labs/lab-10/tasks/overwrite-ret-addr/README.md index d571090b7..ae20ba344 100644 --- a/labs/lab-10/tasks/overwrite-ret-addr/README.md +++ b/labs/lab-10/tasks/overwrite-ret-addr/README.md @@ -33,14 +33,14 @@ In order to verify your exploit, please complete the `exploit.py` TODOs. You can test it using this command: ```console -student@hsi:/.../overwrite-ret-addr/support python3 exploit.py | ./break_this +student@hsi:~/.../tasks/overwrite-ret-addr/support$ python3 exploit.py | ./break_this [...] ``` Afterwards, navigate to the `tests` directory and run: ```console -student@hsi:/.../overwrite-ret-addr/tests make check +student@hsi:~/.../tasks/overwrite-ret-addr/tests$ make check test........................................passed Total: 100/100 diff --git a/labs/lab-10/tasks/overwrite-ret-addr/solution/README.md b/labs/lab-10/tasks/overwrite-ret-addr/solution/README.md index 78afdb229..8922f41e1 100644 --- a/labs/lab-10/tasks/overwrite-ret-addr/solution/README.md +++ b/labs/lab-10/tasks/overwrite-ret-addr/solution/README.md @@ -24,7 +24,7 @@ First use this command to scan the executable: We can find the address of the `magic_function()` using this command: ```console -student@hsi:/.../overwrite-ret-addr/support$ nm break_this | grep magic_function +student@hsi:~/.../tasks/overwrite-ret-addr/support$ nm break_this | grep magic_function 080491d6 T magic_function ``` diff --git a/labs/lab-11/guides/cpp-obs/README.md b/labs/lab-11/guides/cpp-obs/README.md index 8d9ad7668..7b63d6505 100644 --- a/labs/lab-11/guides/cpp-obs/README.md +++ b/labs/lab-11/guides/cpp-obs/README.md @@ -15,10 +15,10 @@ This occurs because C++ symbols are *mangled*. If we use the `nm` command on object modules obtained from C source code, we get: ```console -$ nm add.o +student@hsi:~/.../guides/cpp-obs/support$ nm add.o 0000000000000000 T _Z3addii -$ nm sub.o +student@hsi:~/.../guides/cpp-obs/support$ nm sub.o 0000000000000000 T _Z3subii ``` diff --git a/labs/lab-11/tasks/entry-fix-1/README.md b/labs/lab-11/tasks/entry-fix-1/README.md index 407ac1672..e375fa893 100644 --- a/labs/lab-11/tasks/entry-fix-1/README.md +++ b/labs/lab-11/tasks/entry-fix-1/README.md @@ -20,13 +20,13 @@ These solutions instead modify the build system to use a different function, oth **Checker**: To test the implementation, enter the tests/ directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/entry-fix-1/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/entry-fix-1/tests$ ./run_all_tests.sh test_a-c ........................ passed ... 25 test_b-asm ........................ passed ... 25 diff --git a/labs/lab-11/tasks/entry-fix-2/README.md b/labs/lab-11/tasks/entry-fix-2/README.md index eb0ea8178..b8304fcaa 100644 --- a/labs/lab-11/tasks/entry-fix-2/README.md +++ b/labs/lab-11/tasks/entry-fix-2/README.md @@ -11,13 +11,13 @@ Run the `make` command, interpret the encountered error, and resolve it by editi **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/entry-fix-2/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/entry-fix-2/tests$ ./run_all_tests.sh test_EntryFix2 ........................ passed ... 100 diff --git a/labs/lab-11/tasks/export-fix/README.md b/labs/lab-11/tasks/export-fix/README.md index ce713aa19..f5daf03e9 100644 --- a/labs/lab-11/tasks/export-fix/README.md +++ b/labs/lab-11/tasks/export-fix/README.md @@ -12,13 +12,13 @@ In each subdirectory, run the `make` command, identify the issue, and edit the n **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/export-fix/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/export-fix/tests$ ./run_all_tests.sh test_a-func ........................ passed ... 30 test_b-var ........................ passed ... 30 diff --git a/labs/lab-11/tasks/include-fix/README.md b/labs/lab-11/tasks/include-fix/README.md index 7b1d3bfb4..9e32071e7 100644 --- a/labs/lab-11/tasks/include-fix/README.md +++ b/labs/lab-11/tasks/include-fix/README.md @@ -15,13 +15,13 @@ Resolve this warning by editing the `hello.c` file. **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/include-fix/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/include-fix/tests$ ./run_all_tests.sh test_warning ........................ passed ... 100 diff --git a/labs/lab-11/tasks/lib-fix/README.md b/labs/lab-11/tasks/lib-fix/README.md index 1dc8b91ab..e69699a2f 100644 --- a/labs/lab-11/tasks/lib-fix/README.md +++ b/labs/lab-11/tasks/lib-fix/README.md @@ -12,13 +12,13 @@ Refer to the `Makefile` in the directory `tasks/multiple-link/support/example/c- **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/lib-fix/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/lib-fix/tests$ ./run_all_tests.sh test_library_issue ........................ passed ... 100 diff --git a/labs/lab-11/tasks/multiple-link/README.md b/labs/lab-11/tasks/multiple-link/README.md index a26578b35..5217b2880 100644 --- a/labs/lab-11/tasks/multiple-link/README.md +++ b/labs/lab-11/tasks/multiple-link/README.md @@ -24,13 +24,13 @@ Copy the `Makefile` files and update them in each subdirectory to obtain the exe **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/multiple-link/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/multiple-link/tests$ ./run_all_tests.sh test_a-no-header ........................ passed ... 100 test_b-header ........................ passed ... 100 diff --git a/labs/lab-11/tasks/obj-link-dev/README.md b/labs/lab-11/tasks/obj-link-dev/README.md index 000214c90..445842259 100644 --- a/labs/lab-11/tasks/obj-link-dev/README.md +++ b/labs/lab-11/tasks/obj-link-dev/README.md @@ -19,13 +19,13 @@ Explore the interface and the content of the functions in the `shop.o` file usin **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/obj-link-dev/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/obj-link-dev/tests$ ./run_all_tests.sh test_linking-object-file ........................ passed ... 100 diff --git a/labs/lab-11/tasks/single-link/README.md b/labs/lab-11/tasks/single-link/README.md index 91beeaebb..46ba99efd 100644 --- a/labs/lab-11/tasks/single-link/README.md +++ b/labs/lab-11/tasks/single-link/README.md @@ -39,13 +39,13 @@ Copy the `Makefile` files and update them in each subdirectory to obtain the exe **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/single-link/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/single-link/tests$ ./run_all_tests.sh test_a-dynamic ........................ passed ... 100 test_b-static ........................ passed ... 100 diff --git a/labs/lab-11/tasks/var-func-fix/README.md b/labs/lab-11/tasks/var-func-fix/README.md index ec48e8765..aca54482c 100644 --- a/labs/lab-11/tasks/var-func-fix/README.md +++ b/labs/lab-11/tasks/var-func-fix/README.md @@ -11,13 +11,13 @@ Run the `make` command, run the resulted executable, interpret the encountered e **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/var-func-fix/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/var-func-fix/tests$ ./run_all_tests.sh test_var-func-fix ........................ passed ... 100 diff --git a/labs/lab-11/tasks/vars-obs/README.md b/labs/lab-11/tasks/vars-obs/README.md index 19a098893..fff2e7ee8 100644 --- a/labs/lab-11/tasks/vars-obs/README.md +++ b/labs/lab-11/tasks/vars-obs/README.md @@ -24,13 +24,13 @@ Modify `main.c` such that `hidden_value` is set to 10 and `age` is set to 33. **Checker**: To test the implementation, enter the `tests/` directory and run: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/vars-obs/tests$ ./run_all_tests.sh ``` In case of a correct solution, you will get this output: ```console -./run_all_tests.sh +student@hsi:~/.../tasks/vars-obs/tests$ ./run_all_tests.sh test_vars-obs ........................ passed ... 100 diff --git a/labs/lab-12/tasks/feeling-chained/README.md b/labs/lab-12/tasks/feeling-chained/README.md index 2c0c0ef3d..941d5c8cc 100644 --- a/labs/lab-12/tasks/feeling-chained/README.md +++ b/labs/lab-12/tasks/feeling-chained/README.md @@ -17,7 +17,7 @@ The previously mentioned [online example](https://medium.com/@0x-Singularity/exp To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/feeling-chained/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-12/tasks/indirect-business/README.md b/labs/lab-12/tasks/indirect-business/README.md index d412c0513..0e1cf42a9 100644 --- a/labs/lab-12/tasks/indirect-business/README.md +++ b/labs/lab-12/tasks/indirect-business/README.md @@ -18,7 +18,7 @@ If that still doesn't work, keep in mind that the great cybersecurity expert nam To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/indirect-business/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-12/tasks/rip-my-buffers-off/README.md b/labs/lab-12/tasks/rip-my-buffers-off/README.md index a5e03de18..7c17de3fb 100644 --- a/labs/lab-12/tasks/rip-my-buffers-off/README.md +++ b/labs/lab-12/tasks/rip-my-buffers-off/README.md @@ -16,7 +16,7 @@ The `rip-my-buffers-off/support/buff-ovf2` binary does not use the `get_flag()` To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/rip-my-buffers-off/tests$ make check ``` In case of a correct solution, you will get an output such as: diff --git a/labs/lab-12/tasks/rop/README.md b/labs/lab-12/tasks/rop/README.md index b93da5fd0..3dc68db47 100644 --- a/labs/lab-12/tasks/rop/README.md +++ b/labs/lab-12/tasks/rop/README.md @@ -21,7 +21,7 @@ In `pwndbg`, you can use something like `rop --grep "pop rsi"`. To test the implementation, enter the `tests/` directory and run: ```console -make check +student@hsi:~/.../tasks/rop/tests$ make check ``` In case of a correct solution, you will get an output such as: