Docker

Note: this was converted from Typst to Markdown using AI assistance. The original Typst file can be found here along with the bibliography. Exercise 1: Anti Hardening Laboratory protocol Exercise 1: Anti Hardening Figure: Grouplogo Subject: ITSI Class: 4AHITN Name: Dan Eduard Leuska, Justin Tremurici, Stefan Fürst Group Name/Number: Die Goons / 1 Supervisor: ZIVK, SPAC Exercise dates: 22.09.25, 29.09.25, 06.10.25, 13.10.25 Submission date: 20.10.25 Table of Contents Summary Complete network topology of the exercise Exercise Execution Setup Architecture Connecting the Setup Using Tailscale Choosing Distros How Alpine is different from Debian Setting Up Alpine Setting Up Debian Setting Up Windows Server Setting Up the Services Setting Up PostgreSQL Database Schema Setting Up the API Setting Up the Frontend Setting Up Kubernetes Setting Up Docker Swarm Setting Up SMB Share Making the Application Insecure Authentication Bypass via JWT Parsing Authentication Bypass via HTTP Headers CSP Header Misconfiguration Hardcoding Secrets Database Listening on All Interfaces Making Windows Insecure Changing The Execution Policy Disabling Windows Defender Making Linux Insecure Disabling ASLR Writable Binaries How Tools Like Tailscale Help Harden Security References Summary This exercise is about hardening and then anti-hardening server applications and OSes, so a fictional app was created that features the requirements of having a database and a webserver. Everything was hosted on a laptop in VirtualBox with NAT networking and connected over Tailscale as will be further explained in Connecting the Setup Using Tailscale. ...

The code for all setups is available on my GitHub here. Docker crash course What is docker? Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. With Docker, you can manage your infrastructure in the same ways you manage your applications. By taking advantage of Docker’s methodologies for shipping, testing, and deploying code, you can significantly reduce the delay between writing code and running it in production. ...

Note: this was converted from LaTeX to Markdown using manual formatting. The original TeX file can be found here along with the bibliography. GNU/Linux - Setting up a multi-user environment Laboratory Protocol GNU/Linux - Setting up a multi-user environment Figure: Grouplogo Subject: ITSI|ZIVK Class: 3AHITN Name: Stefan Fürst, Marcel Raichle Group Name/Number: Dumm und Dümmer/7 Supervisor: ZIVK Exercise dates: 25.10.2024, 1.11.2024, 3.11.2024, 6.11.2024 Submission date: 6.11.2024 Table of Contents Task Definition Summary Exercise Execution Creating the Container Testing Connectivity It works, but why? Creating and managing users Login as the users Set directory privileges Setting up ssh Logging On to the SSH Server Enabling keypair authentication Disable password authentication References List of Figures Attachments Task Definition Setting up a headless Linux installation with multiple users, adding them to a group, and setting permissions over a directory structure. You will also need to set up an ssh server for which you will need to set up key pair authentication. ...