diff --git a/graphs/.$kicksecure.drawio.bkp b/graphs/.$kicksecure.drawio.bkp
new file mode 100644
index 0000000..14cb875
--- /dev/null
+++ b/graphs/.$kicksecure.drawio.bkp
@@ -0,0 +1,210 @@
+
Next, we make sure that unattended upgrades are activated so that minor package updates are automatically carried out by the system.
-nihilist@debian:~$ sudo apt install unattended-upgrades apt-listchanges -y
-nihilist@debian:~$ sudo dpkg-reconfigure -plow unattended-upgrades
+[user ~]%:~$ sudo apt install unattended-upgrades apt-listchanges -y
+[user ~]%:~$ sudo dpkg-reconfigure -plow unattended-upgrades
Next, we're going to trim out what we don't need from our Host OS. First and foremost, let's get rid of all the logs (both system and kernel logs) on the system.
-nihilist@debian:~$ su -
+[user ~]%:~$ su -
root@debian:~# crontab -e # run it as the root user!
* * * * * echo "" > /var/log/*.log /var/log/*/*.log /var/log/*/*/*.log ; dmesg -c ; dmesg -n 1 ; dmesg -c
@@ -142,25 +142,25 @@ kernel.printk = 3 4 1 3
Virtualisation setup
Next we do not virtualize anything using closed-source software like VMWare Workstation or else. We use QEMU/KVM with virt-manager, which is an open source hypervisor:
-nihilist@debian:~# sudo apt install libvirt0 virt-manager dnsmasq bridge-utils
+[user ~]%:~# sudo apt install libvirt0 virt-manager dnsmasq bridge-utils
sudo systemctl enable --now libvirtd
-nihilist@debian:~# sudo usermod -a -G libvirt nihilist
-nihilist@debian:~# sudo usermod -a -G kvm nihilist
+[user ~]%:~# sudo usermod -a -G libvirt user
+[user ~]%:~# sudo usermod -a -G kvm user
-nihilist@debian:~# sudo vim /etc/libvirt/libvirtd.conf
-nihilist@debian:~# cat /etc/libvirt/libvirtd.conf | grep sock_group
+[user ~]%:~# sudo vim /etc/libvirt/libvirtd.conf
+[user ~]%:~# cat /etc/libvirt/libvirtd.conf | grep sock_group
unix_sock_group = "libvirt"
unix_sock_rw_perms = "0770"
-nihilist@debian:~# cat /etc/libvirt/qemu.conf
+[user ~]%:~# cat /etc/libvirt/qemu.conf
group = "libvirt"
-user = "nihilist"
+user = "user"
-nihilist@debian:~# systemctl restart libvirtd.service
+[user ~]%:~# systemctl restart libvirtd.service
-nihilist@debian:~# virt-manager
+[user ~]%:~# virt-manager
Next just make sure that the NAT network is created, and that the ISOs and VMs folders are with the correct permissions:
@@ -169,14 +169,14 @@ nihilist@debian:~# virt-manager
That way, the adversary that can normally see what's going on in the network attached to the Windows VM can no longer see as it is being put in a different network altogether.
-nihilist@debian:~$ mkdir ISOs
-nihilist@debian:~$ mkdir VMs
+[user ~]%:~$ mkdir ISOs
+[user ~]%:~$ mkdir VMs
-nihilist@debian:~$ sudo chmod 770 -R VMs
-nihilist@debian:~$ sudo chmod 770 -R ISOs
+[user ~]%:~$ sudo chmod 770 -R VMs
+[user ~]%:~$ sudo chmod 770 -R ISOs
-nihilist@debian:~$ sudo chown nihilist:libvirt -R VMs
-nihilist@debian:~$ sudo chown nihilist:libvirt -R ISOs
+[user ~]%:~$ sudo chown nihilist:libvirt -R VMs
+[user ~]%:~$ sudo chown nihilist:libvirt -R ISOs
Then you can add the file directories in virt-manager like so:
@@ -197,7 +197,7 @@ nihilist@debian:~$ sudo chown nihilist:libvirt -R ISOs
- How to setup Vms for Public and Private use
+ How to setup the Public use VM
Next, Bob needs to use VMs for 2 basic needs: Public internet usage, and Private internet usage. He first needs to download the Windows ISO file, and the debian iso file too:
First he creates the windows VM like so:
@@ -215,17 +215,52 @@ nihilist@debian:~$ sudo chown nihilist:libvirt -R ISOs
-Then he creates the debian VM like so:
-
-
-Then in both VMs he installs the OS on the virtual disk:
+Then in the windows VM he installs the OS on the virtual disk:
-Then Bob can launch both VMs (make sure that the VM boots onto the disk instead of the iso in the boot settings):
+Then Bob can launch the windows VM (make sure that the VM boots onto the disk instead of the iso in the boot settings):
-Then Bob can use the windows VM for his public usage (such as KYC services, and closed-source software), and use the debian VM for his private usage (any personal matter, with only open source software)
-From inside the Debian VM, you can run the following from a terminal to be able to copy and paste from inside the VM out, and from outside the VM in:
+Then Bob can use the windows VM for his public usage (such as KYC services, and closed-source software). Keep in mind that the windows VM is the place where the big eye of sauron can see what you are doing. NEVER do anything sensitive from this VM, because you will never have any privacy in it.
+
+
+
+
+
+
+
+
+
+
+
+
+ How to setup the Private use VM
+To setup the Private use VM, we'll download the Kicksecure ISO just like we previously did in the host OS tutorial, except this time we'll directly attach it to a new VM:
+
+
+
+
+
+
+
+From there you can repeat the steps that we took to install kicksecure on the host OS, to install it:
+
+
+
+
+
+
+Once here, we reboot the VM, and upon rebooting we unlock the encrypted system drive:
+
+
+
+
+
+
+ And from here we have our private VM setup! Warning: You only have privacy in this VM, as long as you do not install any closed-source software (ex: no discord, no google chrome, etc) in it! Make sure that you ONLY install FOSS software in the private VM. Any closed-source software you want to install needs to be installed in the Public VM instead.
+
+
+
+Next, Bob can setup a VPN by default into his kicksecure VM to prevent his ISP from spying on what he is doing.
diff --git a/opsec/index.html b/opsec/index.html
index 5eba249..69fd469 100644
--- a/opsec/index.html
+++ b/opsec/index.html
@@ -116,7 +116,7 @@
💻 Getting started
- - ✅ How to have Privacy on your Computer (Linux) ⭐


+ - ✅ How to have Privacy on your Computer (Kicksecure) ⭐


- ✅ How to have Privacy on your Phone (GrapheneOS)


- ❌ How to have Privacy on your Router (Openwrt)


- 🚧 Easy Private Chats - SimpleX


diff --git a/opsec/internetsegmentation/2.png b/opsec/internetsegmentation/2.png
index cb2a837..77cedf2 100644
Binary files a/opsec/internetsegmentation/2.png and b/opsec/internetsegmentation/2.png differ
diff --git a/opsec/internetsegmentation/3.png b/opsec/internetsegmentation/3.png
index c88fe16..1d094d2 100644
Binary files a/opsec/internetsegmentation/3.png and b/opsec/internetsegmentation/3.png differ
diff --git a/opsec/internetsegmentation/4.png b/opsec/internetsegmentation/4.png
index 51e90eb..c0a3a22 100644
Binary files a/opsec/internetsegmentation/4.png and b/opsec/internetsegmentation/4.png differ
diff --git a/opsec/internetsegmentation/5.png b/opsec/internetsegmentation/5.png
index b146fe6..53edcfa 100644
Binary files a/opsec/internetsegmentation/5.png and b/opsec/internetsegmentation/5.png differ
diff --git a/opsec/internetsegmentation/6.png b/opsec/internetsegmentation/6.png
index 69f3554..fb449f3 100644
Binary files a/opsec/internetsegmentation/6.png and b/opsec/internetsegmentation/6.png differ
diff --git a/opsec/linux/10.png b/opsec/linux/10.png
index c7d4814..ac9d5f7 100644
Binary files a/opsec/linux/10.png and b/opsec/linux/10.png differ
diff --git a/opsec/linux/11.1.png b/opsec/linux/11.1.png
new file mode 100644
index 0000000..7465e6d
Binary files /dev/null and b/opsec/linux/11.1.png differ
diff --git a/opsec/linux/11.2.png b/opsec/linux/11.2.png
new file mode 100644
index 0000000..8dcf150
Binary files /dev/null and b/opsec/linux/11.2.png differ
diff --git a/opsec/linux/11.png b/opsec/linux/11.png
index e607b17..3cbe656 100644
Binary files a/opsec/linux/11.png and b/opsec/linux/11.png differ
diff --git a/opsec/linux/12.png b/opsec/linux/12.png
index 6ad5aa0..1bb25e3 100644
Binary files a/opsec/linux/12.png and b/opsec/linux/12.png differ
diff --git a/opsec/linux/13.png b/opsec/linux/13.png
index 091d497..c879fc2 100644
Binary files a/opsec/linux/13.png and b/opsec/linux/13.png differ
diff --git a/opsec/linux/22.png b/opsec/linux/22.png
index abafa3f..9a39257 100644
Binary files a/opsec/linux/22.png and b/opsec/linux/22.png differ
diff --git a/opsec/linux/23.png b/opsec/linux/23.png
index 3789907..fd9c1f2 100644
Binary files a/opsec/linux/23.png and b/opsec/linux/23.png differ
diff --git a/opsec/linux/24.png b/opsec/linux/24.png
index e729bb7..f8de262 100644
Binary files a/opsec/linux/24.png and b/opsec/linux/24.png differ
diff --git a/opsec/linux/25.png b/opsec/linux/25.png
index b9240a4..64bcb2b 100644
Binary files a/opsec/linux/25.png and b/opsec/linux/25.png differ
diff --git a/opsec/linux/26.png b/opsec/linux/26.png
index 27cca4f..1f0079c 100644
Binary files a/opsec/linux/26.png and b/opsec/linux/26.png differ
diff --git a/opsec/linux/28.png b/opsec/linux/28.png
index 1801beb..b379531 100644
Binary files a/opsec/linux/28.png and b/opsec/linux/28.png differ
diff --git a/opsec/linux/3.png b/opsec/linux/3.png
index dfd3155..eb496f6 100644
Binary files a/opsec/linux/3.png and b/opsec/linux/3.png differ
diff --git a/opsec/linux/4.png b/opsec/linux/4.png
index b01423c..9e1d72e 100644
Binary files a/opsec/linux/4.png and b/opsec/linux/4.png differ
diff --git a/opsec/linux/5.png b/opsec/linux/5.png
index fc694fd..7cb3f26 100644
Binary files a/opsec/linux/5.png and b/opsec/linux/5.png differ
diff --git a/opsec/linux/52.png b/opsec/linux/52.png
index 32bd463..a656eea 100644
Binary files a/opsec/linux/52.png and b/opsec/linux/52.png differ
diff --git a/opsec/linux/53.png b/opsec/linux/53.png
index ba27ee5..6d28f39 100644
Binary files a/opsec/linux/53.png and b/opsec/linux/53.png differ
diff --git a/opsec/linux/56.png b/opsec/linux/56.png
index 3e02b55..ca985ad 100644
Binary files a/opsec/linux/56.png and b/opsec/linux/56.png differ
diff --git a/opsec/linux/6.png b/opsec/linux/6.png
index 43155d9..bdc20a9 100644
Binary files a/opsec/linux/6.png and b/opsec/linux/6.png differ
diff --git a/opsec/linux/7.png b/opsec/linux/7.png
index d9d8b90..68454a4 100644
Binary files a/opsec/linux/7.png and b/opsec/linux/7.png differ
diff --git a/opsec/linux/8.png b/opsec/linux/8.png
index 4962545..2a0fac7 100644
Binary files a/opsec/linux/8.png and b/opsec/linux/8.png differ
diff --git a/opsec/linux/9.png b/opsec/linux/9.png
index bac9733..62df047 100644
Binary files a/opsec/linux/9.png and b/opsec/linux/9.png differ
diff --git a/opsec/linux/index.html b/opsec/linux/index.html
index 6542cdc..f482409 100644
--- a/opsec/linux/index.html
+++ b/opsec/linux/index.html
@@ -63,7 +63,7 @@
Previous Page
nihilist@mainpc - 2024-06-16
How to have Privacy on your Computer (Linux)
-In this tutorial, we're going to look at the first and foremost thing anyone can do to remove surveillance from their digital lives, by installing a free and open source software (FOSS) host operating system: Linux, in this case we're going to setup the latest Debian.
+In this tutorial, we're going to look at the first and foremost thing anyone can do to remove surveillance from their digital lives, by installing a free and open source software (FOSS) host operating system: Linux, in this case we're going to setup the latest Kicksecure host OS, since it is a secure-by-default linux distribution.
OPSEC Recommendations:
Hardware : (Personal Computer / Laptop)
@@ -105,33 +105,29 @@
- How to create a Debian USB installer from Windows?
-First Bob, goes on the web to find a Linux distribution he likes, that is Open Source:
+ How to create a Linux USB installer from Windows?
+First step is to go on the web to find a secure linux distribution such as Kicksecure:
-He sees there are many options like Linux Mint, Ubuntu, etc
-But he settles on Debian. (Disclaimer: if you use closed-source hardware, like 99.9999999999% of people out there, you will invariably have to use non-free firmware too [1] [2] [3]). If you want a purely FOSS host OS, and you are willing to not have firmware for your CPU, GPU, Motherboard, Ethernet/wifi, check out the OSes recommended by the Free Software Foundation [4] (but it will be at the expense of having your peripherals not working [5]). The status of Open source Hardware is not even competitive in this closed-source hardware domination of the market., hopefully this will change in the future, but for now that's how it is. TLDR: If you don't want to install proprietary firmware, check out PureOS instead of debian.
+So we're going to install Kicksecure. (Disclaimer: if you use closed-source hardware, like 99.9999999999% of people out there, you will invariably have to use non-free firmware too [1] [2] [3]). If you want a purely FOSS host OS, and you are willing to not have firmware for your CPU, GPU, Motherboard, Ethernet/wifi, check out the OSes recommended by the Free Software Foundation [4] (but it will be at the expense of having your peripherals not working [5]). The status of Open source Hardware is not even competitive in this closed-source hardware domination of the market., hopefully this will change in the future, but for now that's how it is. TLDR: If you don't want to install proprietary firmware, check out PureOS instead of Kicksecure.
-Now Bob has the Debian ISO image.
+Let it download and then we have the Kicksecure ISO image.
-But now he needs to put that ISO image on a USB stick. To do so he can use Rufus or Balena Etcher:
+But now we need to put that ISO image on a USB stick. To do so we can use Rufus:
-So Bob installs BalenaEtcher:
+next we install Rufus and plug in a usb stick in the computer (Warning: the usb stick should be at least 2 GB big):
+And once the kicksecure iso image finishes downloading, we use it from inside rufus by clicking the "select" button:
-Once installed, he selects the ISO image in balenaetcher:
+And lastly we click "start" to
-Then, Bob plugs in his USB stick in his computer, to be able to put the ISO image into it:
+
+
-Then, Bob selects his USB stick from balenaetcher:
+Then we wait a few minutes, and now we have a USB stick with the latest Kicksecure OS on it:
-Then he clicks "Flash", that way Balenaetecher will put the ISO image on the USB stick.
-
-
-Bob waits a few minutes, and now he has a USB stick with the latest Debian OS on it.
-
-Bob will now be able to use it to install Linux and replace Windows with it.
+And now we will be able to use it to install Linux and replace Windows with it.
@@ -144,16 +140,16 @@
- How to use the Debian USB stick to overwrite Windows ?
+ How to use the kicksecure USB stick to overwrite Windows ?
This is where it gets a bit technical for Bob. But here are the steps he needs to do:
He needs to plug his USB stick in his computer
He needs to restart his computer
As his computer restarts, he needs to repeatedly press the F1 or F2 or DEL or F10 key in order to enter his computer's BIOS (depending on which brand his computer is)
- once he is in the BIOS, he then needs to boot on his USB stick that has the Debian image
- Then once he boots on his USB stick, he can install debian on his computer
+ once he is in the BIOS, he then needs to boot on his USB stick that has the kicksecure image
+ Then once he boots on his USB stick, he can install kicksecure on his computer
-The key that Bob needs to press to enter his computer's BIOS depends on what brand his computer is (see this blogpost for examples).
+The key that we need to press to enter his computer's BIOS depends on what brand his computer is (see this blogpost for examples).
Now Bob restarts his computer:
And now, as he has an ASUS motherboard, he repeatedly presses the F2 key to enter his computer's BIOS:
@@ -165,52 +161,22 @@
Boot device Selection > his USB stick
-Once he selects his USB Stick, Bob can now boot from it, and he is greeted by Debian's welcome screen:
+Once we selects his USB Stick, Bob can now boot from it, and he is greeted by kicksecure's welcome screen:
And from there, Bob installs linux as per his needs:
-
-
-
-
-Here Bob decides that he wants to encrypt his whole harddrive too. That way, if someone were to steal his computer, without knowing his password, they would have no way to access Bob's local data. (but be warned that for sensitive use, one shouldn't need to encrypt the system drive at all (more details).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Here Bob can select his window manager. Gnome is the default option, but he chooses Cinnamon to keep the feel similar to how it was on windows.
-
-
-
-
-
-And there, Bob finished the Debian installation, he can unplug his USB stick, and click Continue to reboot his computer:
+And there, we finished the kicksecure installation, we can unplug the USB stick, and click done to reboot the computer, into the newly installed kicksecure Host OS:
-As he reboots his computer, he is greeted by the Debian boot screen, and he then types his password to unlock his harddrive encryption:
+As we reboot the computer, we're greeted by the kicksecure boot screen, and then we type the password to unlock the encrypted system drive:
-
-Then he logs in using the password he set earlier:
-
-And now that Bob is logged in, he is greeted by the Cinnamon window manager, the feel of his OS remains similar to what he previously had on Windows, but now it's all open source!
+And now that we are logged, we're in our brand new kicksecure operating system, with the XFCE window manager, You now have a secure-by-default linux host OS, and now it's all open source! This means that you no longer have windows's countless cameras spying on what you were doing. You now have privacy on your computer.
And that's it! Bob has managed to get privacy from Microsoft's constant surveillance by replacing Windows with a Linux distribution.
-From there, Bob can update his linux distribution and install new packages, following this tutorial here.
diff --git a/opsec/logos/kicksecure.png b/opsec/logos/kicksecure.png
new file mode 100644
index 0000000..4a1a30f
Binary files /dev/null and b/opsec/logos/kicksecure.png differ
diff --git a/opsec/logos/waindowz.png b/opsec/logos/waindowz.png
new file mode 100644
index 0000000..78ce9d1
Binary files /dev/null and b/opsec/logos/waindowz.png differ
diff --git a/opsec/logos/winblows.png b/opsec/logos/winblows.png
new file mode 100644
index 0000000..d0ae414
Binary files /dev/null and b/opsec/logos/winblows.png differ
diff --git a/opsec/logos/windows.jpeg b/opsec/logos/windows.jpeg
new file mode 100644
index 0000000..36fefa7
Binary files /dev/null and b/opsec/logos/windows.jpeg differ