mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-12-15 07:53:07 -05:00
Change URIs from CamelCase to lowercase-hyphen-separated
This commit is contained in:
Axon
parent
bb5fb46527
commit
f3ee78f223
160 changed files with 888 additions and 579 deletions
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: AssigningDevices
|
||||
permalink: /doc/AssigningDevices/
|
||||
redirect_from: /wiki/AssigningDevices/
|
||||
permalink: /en/doc/assigning-devices/
|
||||
redirect_from:
|
||||
- /doc/AssigningDevices/
|
||||
- /wiki/AssigningDevices/
|
||||
---
|
||||
|
||||
Assigning Devices to VMs
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
layout: doc
|
||||
title: ConfigFiles
|
||||
permalink: /doc/ConfigFiles/
|
||||
permalink: /en/doc/config-files/
|
||||
redirect_from:
|
||||
- /doc/ConfigFiles/
|
||||
- "/doc/UserDoc/ConfigFiles/"
|
||||
- "/wiki/UserDoc/ConfigFiles/"
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: DiskTRIM
|
||||
permalink: /doc/DiskTRIM/
|
||||
redirect_from: /wiki/DiskTRIM/
|
||||
permalink: /en/doc/disk-trim/
|
||||
redirect_from:
|
||||
- /doc/DiskTRIM/
|
||||
- /wiki/DiskTRIM/
|
||||
---
|
||||
|
||||
VMs have already TRIM enabled by default, but dom0 doesn't. There are some security implications (read for example [this article](http://asalor.blogspot.com/2011/08/trim-dm-crypt-problems.html)), but IMO not very serious.
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: ExternalAudio
|
||||
permalink: /doc/ExternalAudio/
|
||||
redirect_from: /wiki/ExternalAudio/
|
||||
permalink: /en/doc/external-audio/
|
||||
redirect_from:
|
||||
- /doc/ExternalAudio/
|
||||
- /wiki/ExternalAudio/
|
||||
---
|
||||
|
||||
Using External Audio Devices
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: ExternalDeviceMountPoint
|
||||
permalink: /doc/ExternalDeviceMountPoint/
|
||||
redirect_from: /wiki/ExternalDeviceMountPoint/
|
||||
permalink: /en/doc/external-device-mount-point/
|
||||
redirect_from:
|
||||
- /doc/ExternalDeviceMountPoint/
|
||||
- /wiki/ExternalDeviceMountPoint/
|
||||
---
|
||||
|
||||
All external storage devices connected to an AppVM using the Fedora template can be found under
|
||||
|
|
|
|||
|
|
@ -1,14 +1,16 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Fetchmail
|
||||
permalink: /doc/Fetchmail/
|
||||
redirect_from: /wiki/Fetchmail/
|
||||
permalink: /en/doc/fetchmail/
|
||||
redirect_from:
|
||||
- /doc/Fetchmail/
|
||||
- /wiki/Fetchmail/
|
||||
---
|
||||
|
||||
Fetchmail
|
||||
=========
|
||||
|
||||
Fetchmail is standalone MRA (Mail Retrieval Agent) aka "IMAP/POP3 client". Its sole purpose is to fetch your messages and store it locally or feed to local MTA (Message Transfer Agent). It cannot "read" messages — for that, use a MUA like Thunderbird or [Mutt](/doc/Mutt/).
|
||||
Fetchmail is standalone MRA (Mail Retrieval Agent) aka "IMAP/POP3 client". Its sole purpose is to fetch your messages and store it locally or feed to local MTA (Message Transfer Agent). It cannot "read" messages — for that, use a MUA like Thunderbird or [Mutt](/en/doc/mutt/).
|
||||
|
||||
Installation
|
||||
------------
|
||||
|
|
@ -20,7 +22,7 @@ Configuration
|
|||
|
||||
Assuming you have more than one account (safe assumption these days), you need to spawn multiple fetchmail instances, one for each IMAP/POP3 server (though one instance can watch over several accounts on one server). The easiest way is to create template systemd unit and start it several times. Fedora does not supply any, so we have to write one anyway.
|
||||
|
||||
**NOTE:** this assumes you use [Postfix](/doc/Postfix/) as your local MTA.
|
||||
**NOTE:** this assumes you use [Postfix](/en/doc/postfix/) as your local MTA.
|
||||
|
||||
In TemplateVM create `/etc/systemd/system/fetchmail@.service`:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Mutt
|
||||
permalink: /doc/Mutt/
|
||||
redirect_from: /wiki/Mutt/
|
||||
permalink: /en/doc/mutt/
|
||||
redirect_from:
|
||||
- /doc/Mutt/
|
||||
- /wiki/Mutt/
|
||||
---
|
||||
|
||||
Mutt
|
||||
|
|
@ -13,8 +15,8 @@ Mutt is a fast, standards-compliant, efficient MUA (Mail User Agent). In some ar
|
|||
Mutt lacks true MTA (Message Transfer Agent aka "SMTP client") and MRA (Mail
|
||||
Retrieval Agent aka "IMAP/POP3 client"), thus there are some provisions
|
||||
built-in. In principle it is only mail reader and composer. You may install
|
||||
true MTA such as [Postfix](/doc/Postfix/) or Exim and MRA such as
|
||||
[Fetchmail](/doc/Fetchmail/). Alternatively you can synchronize your mailbox
|
||||
true MTA such as [Postfix](/en/doc/postfix/) or Exim and MRA such as
|
||||
[Fetchmail](/en/doc/fetchmail/). Alternatively you can synchronize your mailbox
|
||||
using [OfflineIMAP](https://github.com/OfflineIMAP/offlineimap) and just stick
|
||||
to integrated SMTP support. You can even use integrated IMAP client, but it is
|
||||
not very convenient.
|
||||
|
|
@ -27,7 +29,7 @@ Installation
|
|||
Configuration
|
||||
-------------
|
||||
|
||||
Mutt generally works out of the box. This configuration guide discusses only Qubes-specific setup. In this example we will have one TemplateVM and several AppVMs. It also takes advantage of [SplitGPG](/doc/UserDoc/SplitGpg/), which is assumed to be already working.
|
||||
Mutt generally works out of the box. This configuration guide discusses only Qubes-specific setup. In this example we will have one TemplateVM and several AppVMs. It also takes advantage of [SplitGPG](/en/doc/split-gpg/), which is assumed to be already working.
|
||||
|
||||
**NOTE:** this requires `qubes-gpg-split >= 2.0.9`. 2.0.8 and earlier contains bug which causes this setup to hang in specific situations and does not allow to list keys.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: NetworkBridgeSupport
|
||||
permalink: /doc/NetworkBridgeSupport/
|
||||
redirect_from: /wiki/NetworkBridgeSupport/
|
||||
permalink: /en/doc/network-bridge-support/
|
||||
redirect_from:
|
||||
- /doc/NetworkBridgeSupport/
|
||||
- /wiki/NetworkBridgeSupport/
|
||||
---
|
||||
|
||||
Network Bridge Support (EXPERIMENTAL and UNSUPPORTED)
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: NetworkPrinter
|
||||
permalink: /doc/NetworkPrinter/
|
||||
redirect_from: /wiki/NetworkPrinter/
|
||||
permalink: /en/doc/network-printer/
|
||||
redirect_from:
|
||||
- /doc/NetworkPrinter/
|
||||
- /wiki/NetworkPrinter/
|
||||
---
|
||||
|
||||
Configuring a network printer for Qubes AppVMs
|
||||
|
|
@ -20,7 +22,7 @@ Security considerations for network printers and drivers
|
|||
|
||||
Some printers require 3rd party drivers, typically downloadable from the vendor's website. Such drivers are typically distributed in a form of ready to install RPM packages. However, they are often unsigned, and additionally the downloads are available via HTTP connections only. As a result, installation of such 3rd party RPMs in a default template VM exposes a risk of compromise of this template VM, which, in turn, leads automatically to compromise of all the AppVMs based on the template. (Again, it's not buggy or malicious drivers that we fear here, but rather malicious installation scripts for those drivers).
|
||||
|
||||
In order to mitigate this risk, one might consider creating a custom template (i.e. clone the original template) and then install the 3rd party, unverified drivers there. Such template might then be made the default template for [Disposable VM creation](/doc/DisposableVms/), which should allow one to print any document by right-clicking on it, choosing "Open in Disposable VM" and print from there. This would allow to print documents from more trusted AppVMs (based on a trusted default template, that is not poisoned by 3rd party printer drivers).
|
||||
In order to mitigate this risk, one might consider creating a custom template (i.e. clone the original template) and then install the 3rd party, unverified drivers there. Such template might then be made the default template for [Disposable VM creation](/en/doc/disposable-vms/), which should allow one to print any document by right-clicking on it, choosing "Open in Disposable VM" and print from there. This would allow to print documents from more trusted AppVMs (based on a trusted default template, that is not poisoned by 3rd party printer drivers).
|
||||
|
||||
However, one should be aware that most (all?) network printing protocols are insecure, unencrypted protocols. This means, that an attacker who is able to sniff the local network, or who is controlling the (normally untrusted) Qubes NetVM, will likely to be able to see the documents being printed. This is a limitation of today's printers and printing protocols, something that cannot be solved by Qubes or any other OS.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,14 +1,16 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Postfix
|
||||
permalink: /doc/Postfix/
|
||||
redirect_from: /wiki/Postfix/
|
||||
permalink: /en/doc/postfix/
|
||||
redirect_from:
|
||||
- /doc/Postfix/
|
||||
- /wiki/Postfix/
|
||||
---
|
||||
|
||||
Postfix
|
||||
=======
|
||||
|
||||
Postfix is full featured MTA (Message Transfer Agent). Here we will configure it in smarthost mode as part of common [Mutt](/doc/Mutt/)+Postfix+[Fetchmail](/doc/Fetchmail/) stack.
|
||||
Postfix is full featured MTA (Message Transfer Agent). Here we will configure it in smarthost mode as part of common [Mutt](/en/doc/mutt/)+Postfix+[Fetchmail](/en/doc/fetchmail/) stack.
|
||||
|
||||
Installation
|
||||
------------
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: ResizeDiskImage
|
||||
permalink: /doc/ResizeDiskImage/
|
||||
redirect_from: /wiki/ResizeDiskImage/
|
||||
permalink: /en/doc/resize-disk-image/
|
||||
redirect_from:
|
||||
- /doc/ResizeDiskImage/
|
||||
- /wiki/ResizeDiskImage/
|
||||
---
|
||||
|
||||
Resizing Disk Image
|
||||
|
|
@ -15,7 +17,7 @@ There are several disk images which can be easily extended.
|
|||
|
||||
1048576 MB is the maximum size which can be assigned to a private storage through qubes-manager.
|
||||
|
||||
To grow the private disk image of a AppVM beyond this limit [qubes-grow-private](/doc/Dom0Tools/QvmGrowPrivate/) can be used:
|
||||
To grow the private disk image of a AppVM beyond this limit [qubes-grow-private](/en/doc/dom0-tools/qvm-grow-private/) can be used:
|
||||
|
||||
~~~
|
||||
qvm-grow-private <vm-name> <size>
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: ResizeRootDiskImage
|
||||
permalink: /doc/ResizeRootDiskImage/
|
||||
redirect_from: /wiki/ResizeRootDiskImage/
|
||||
permalink: /en/doc/resize-root-disk-image/
|
||||
redirect_from:
|
||||
- /doc/ResizeRootDiskImage/
|
||||
- /wiki/ResizeRootDiskImage/
|
||||
---
|
||||
|
||||
Resizing \`root.img\` Size
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Rxvt
|
||||
permalink: /doc/Rxvt/
|
||||
redirect_from: /wiki/Rxvt/
|
||||
permalink: /en/doc/rxvt/
|
||||
redirect_from:
|
||||
- /doc/Rxvt/
|
||||
- /wiki/Rxvt/
|
||||
---
|
||||
|
||||
Rxvt
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: SecondaryStorage
|
||||
permalink: /doc/SecondaryStorage/
|
||||
redirect_from: /wiki/SecondaryStorage/
|
||||
permalink: /en/doc/secondary-storage/
|
||||
redirect_from:
|
||||
- /doc/SecondaryStorage/
|
||||
- /wiki/SecondaryStorage/
|
||||
---
|
||||
|
||||
Storing AppVMs on Secondary Drives
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
---
|
||||
layout: doc
|
||||
title: TorVM
|
||||
permalink: /doc/TorVM/
|
||||
permalink: /en/doc/torvm/
|
||||
redirect_from:
|
||||
- /doc/TorVM/
|
||||
- "/doc/UserDoc/TorVM/"
|
||||
- "/wiki/UserDoc/TorVM/"
|
||||
---
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: VPN
|
||||
permalink: /doc/VPN/
|
||||
redirect_from: /wiki/VPN/
|
||||
permalink: /en/doc/vpn/
|
||||
redirect_from:
|
||||
- /doc/VPN/
|
||||
- /wiki/VPN/
|
||||
---
|
||||
|
||||
How To make a VPN Gateway in Qubes
|
||||
|
|
@ -1,8 +1,10 @@
|
|||
---
|
||||
layout: doc
|
||||
title: ZFS
|
||||
permalink: /doc/ZFS/
|
||||
redirect_from: /wiki/ZFS/
|
||||
permalink: /en/doc/zfs/
|
||||
redirect_from:
|
||||
- /doc/ZFS/
|
||||
- /wiki/ZFS/
|
||||
---
|
||||
|
||||
ZFS in Qubes
|
||||
Loading…
Add table
Add a link
Reference in a new issue