root@portfolio:~$ whoami
Information Security student at THWS Würzburg with a focus on offensive security, secure software engineering, and systems that become more interesting precisely where their assumptions begin to fail.
I care less about collecting shells than understanding the broken assumption that made them possible, how the weakness can be reproduced, and what a real fix should look like.
current signal building security tools
documenting labs
expanding the home lab
working toward deeper offensive-security practice
root@portfolio:~$ ls ~/projects
root@portfolio:~$ find ~/projects -maxdepth 1 -type d
```
The goal is not merely to prove that something breaks, but to explain why it breaks, what assumption failed, how the finding can be reproduced safely, and how the weakness should be fixed. |
<td width="50%" valign="top">
<h2><code>05 // INSTALLED PACKAGES</code></h2>
```text
root@portfolio:~$ pacman -QLanguages Security Systems & Development |
root@portfolio:~$ journalctl --since "365 days ago"
root@portfolio:~$ ls ~/known-routes