fix stuff

This commit is contained in:
nihilist 2025-05-31 10:56:31 +02:00
parent 27ce7974c6
commit b61b3475dc
4 changed files with 101 additions and 4 deletions

View file

@ -1,6 +1,6 @@
--- ---
author: Anonymous author: Anonymous
date: 2025-01-31 date: 2025-05-30
gitea_url: "http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/318" gitea_url: "http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/318"
xmr: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8 xmr: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8
--- ---
@ -41,6 +41,7 @@ For example if you want to order a Dell poweredge server, you can get refurbishe
![alt text](image-3.png) ![alt text](image-3.png)
Or you can get recent ones like the R470 with a hell of a CPU for ultra high-end performance tasks: Or you can get recent ones like the R470 with a hell of a CPU for ultra high-end performance tasks:
![alt text](image-2.png) ![alt text](image-2.png)
**But the main problem is the noise of those servers**, from my own experience, having a poweredge R420 next to you is unbearable, it would have to sit in a separate room altogether. If you don't have a house yet, you may not have the luxury to put that server elsewhere, where it doesn't bother you nor your neighbors. **But the main problem is the noise of those servers**, from my own experience, having a poweredge R420 next to you is unbearable, it would have to sit in a separate room altogether. If you don't have a house yet, you may not have the luxury to put that server elsewhere, where it doesn't bother you nor your neighbors.

View file

@ -0,0 +1,96 @@
---
author: Anonymous
date: 2025-01-31
gitea_url: "http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/issues/260"
xmr: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAUqpZHLrX2VZLH71Jrd9k8
---
# Setting up a QEMU/KVM Hypervisor on your home server
**Sidenote:** this setup depends on the previous setup we showcased in [this tutorial](../homeserver/index.md) as we need the homeserver to have the host OS setup, with both SSH and RDP access.
## Setting up libvirtd QEMU/KVM on the host OS
Via SSH we connect to the homeserver to setup the libvirtd QEMU hypervisor, in order to be able to virtualize machines and segment the intended uses accordingly, just like on the clientside.
![](../context/private_self.png)
```sh
[ localhost ] [ /dev/pts/5 ] [~]
→ ssh wonderland
Enter passphrase for key '/home/user/.ssh/torified':
Linux wonderland 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64
Welcome to Kicksecure (TM)!
https://www.kicksecure.com
Kicksecure Copyright (C) 2012 - 2025 ENCRYPTED SUPPORT LLC
Kicksecure is Freedom Software, and you are welcome to redistribute it under
certain conditions; type "kicksecure-license" <enter> for details.
Kicksecure is a compilation of software packages, each under its own copyright and
license. The exact license terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Kicksecure GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law; for details type "kicksecure-disclaimer" <enter>.
Kicksecure is a derivative of Debian GNU/Linux.
Kicksecure is a research project.
default user account: user
default password: No password required. (Passwordless login.)
Type: "kicksecure" <enter> for help.
Web console: https://wonderland:9090/ or https://10.145.64.173:9090/
Last login: Fri May 30 15:19:00 2025 from 192.168.1.67
[ Wonderland ] [ /dev/pts/4 ] [~]
→ sudo -i
```
From there we can install the following packages to setup the hypervisor:
[user ~]%:~# sudo apt install libvirt0 virt-manager dnsmasq bridge-utils
sudo systemctl enable --now libvirtd
sudo systemctl disable --now dnsmasq
[user ~]%:~# sudo usermod -a -G libvirt user
[user ~]%:~# sudo usermod -a -G kvm user
[user ~]%:~# sudo vim /etc/libvirt/libvirtd.conf
unix_sock_group = "libvirt"
unix_sock_rw_perms = "0770"
:wq
[user ~]%:~# sudo vim /etc/libvirt/qemu.conf
group = "libvirt"
user = "user"
:wq
[user ~]%:~# systemctl restart libvirtd.service
[user ~]%:~# virt-manager
[user ~]%:~$ mkdir ISOs
[user ~]%:~$ mkdir VMs
[user ~]%:~$ sudo chmod 770 -R VMs
[user ~]%:~$ sudo chmod 770 -R ISOs
[user ~]%:~$ sudo chown user:libvirt -R VMs
[user ~]%:~$ sudo chown user:libvirt -R ISOs
## Setting up the cockpit web interface to manage the hypervisor
## Setting up a private VM using cockpit
## Setting up a basic web service on the private VM

View file

@ -96,8 +96,8 @@ That way, the adversary that can normally see what's going on in the network att
[user ~]%:~$ sudo chmod 770 -R VMs [user ~]%:~$ sudo chmod 770 -R VMs
[user ~]%:~$ sudo chmod 770 -R ISOs [user ~]%:~$ sudo chmod 770 -R ISOs
[user ~]%:~$ sudo chown nihilist:libvirt -R VMs [user ~]%:~$ sudo chown user:libvirt -R VMs
[user ~]%:~$ sudo chown nihilist:libvirt -R ISOs [user ~]%:~$ sudo chown user:libvirt -R ISOs

View file

@ -124,7 +124,7 @@ If you want to reuse an image from another tutorial like i just did above (it's
![](../graphene/10.png) ![](../graphene/10.png)
and lastly if you have a CLI step to show, you need to simply copy paste the terminal output in the pre code blocks while still highlighting what's important like so: and lastly if you have a CLI step to show, you need to simply copy paste the terminal output in the code blocks while still highlighting what's important like so: