PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2024-12-22 12:51:34 -05:00
Code

Fix tags

Browse Source 
Signed-off-by: Tommy <contact@tommytran.io>
This commit is contained in:
Tommy 2022-07-27 03:22:46 -04:00 committed by tommytran732
parent eae6aee980
commit a8455d3903
No known key found for this signature in database
GPG Key ID: 060B29EB996BD9F2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/os/Using Lokinet on Qubes OS.md
View File

@ -1,7 +1,7 @@
--- ---
title: "Using Lokinet on Qubes OS" title: "Using Lokinet on Qubes OS"
date: 2022-07-27 date: 2022-07-27
tags: ['Operating Systems', 'Qubes OS', 'anonimity', 'privacy'] tags: ['Operating Systems', 'Qubes OS', 'Anonimity', 'Privacy']
author: Tommy author: Tommy
--- ---
@ -71,4 +71,4 @@ Finally, enable the `lokinet` service:
Just create the AppVM as usual and you would be good to go. There are a few things to keep in mind though: Just create the AppVM as usual and you would be good to go. There are a few things to keep in mind though:
- You should probably set networking to use `sys-firewall`. I have tested using my ProtonVPN ProxyVM for networking, and DNS was not working. Besides, it makes litle sense to attempt such setup anyways, unless you are worried about accidental leaks or a compromised AppVM. - You should probably set networking to use `sys-firewall`. I have tested using my ProtonVPN ProxyVM for networking, and DNS was not working. Besides, it makes litle sense to attempt such setup anyways, unless you are worried about accidental leaks or a compromised AppVM.
- You should give the AppVM the `network-manager` service so that it Lokinet can set up networking properly and get DNS working. - You should give the AppVM the `network-manager` service so that Lokinet can set up networking properly and get DNS working.