mirror of
https://github.com/Qubes-Community/Contents.git
synced 2025-12-15 16:29:18 -05:00
Convert relative official website links to absolute
https://github.com/QubesOS/qubes-issues/issues/4693
This commit is contained in:
Andrew David Wong
parent
e3f40cc91f
commit
15eaa32692
35 changed files with 152 additions and 152 deletions
|
|
@ -19,16 +19,16 @@ To switch, reinstall and uninstall a CentOS TemplateVM that is already installed
|
|||
|
||||
#### After Installing
|
||||
|
||||
After a fresh install, we recommend to [Update the TemplateVM](/doc/software-update-vm/).
|
||||
After a fresh install, we recommend to [Update the TemplateVM](https://www.qubes-os.org/doc/software-update-vm/).
|
||||
|
||||
## Want to contribute?
|
||||
|
||||
* [How can I contribute to the Qubes Project?](/doc/contributing/)
|
||||
* [How can I contribute to the Qubes Project?](https://www.qubes-os.org/doc/contributing/)
|
||||
|
||||
* [Guidelines for Documentation Contributors](/doc/doc-guidelines/)
|
||||
* [Guidelines for Documentation Contributors](https://www.qubes-os.org/doc/doc-guidelines/)
|
||||
|
||||
[switch]: /doc/templates/#switching
|
||||
[reinstall]: /doc/reinstall-template/
|
||||
[uninstall]: /doc/templates/#uninstalling
|
||||
[Minimal TemplateVMs]: /doc/templates/minimal/
|
||||
[Xfce TemplateVMs]: /doc/templates/xfce/
|
||||
[switch]: https://www.qubes-os.org/doc/templates/#switching
|
||||
[reinstall]: https://www.qubes-os.org/doc/reinstall-template/
|
||||
[uninstall]: https://www.qubes-os.org/doc/templates/#uninstalling
|
||||
[Minimal TemplateVMs]: https://www.qubes-os.org/doc/templates/minimal/
|
||||
[Xfce TemplateVMs]: https://www.qubes-os.org/doc/templates/xfce/
|
||||
|
|
|
|||
|
|
@ -19,17 +19,17 @@ To switch, reinstall and uninstall a Gentoo TemplateVM that is already installed
|
|||
|
||||
#### After Installing
|
||||
|
||||
After a fresh install, we recommend to [Update the TemplateVM](/doc/software-update-vm/). We highlight that the template memory/CPU allocation certainly need to be adjusted in some cases. As Gentoo is a *linux source distribution*, the template needs resources to perform updates or installing any packages. By default, each TemplateVM has *2 VCPUs* for *4000 MB Max memory* allocated. If needed, double those values, *4 VCPUs* for *8000 MB Max memory*. For example, it has been observed failing updates or builds with *4 VCPUs* for *4000 MB Max memory* due to out of memory issue. For more general considerations, we refer to the official [Gentoo Handbook].
|
||||
After a fresh install, we recommend to [Update the TemplateVM](https://www.qubes-os.org/doc/software-update-vm/). We highlight that the template memory/CPU allocation certainly need to be adjusted in some cases. As Gentoo is a *linux source distribution*, the template needs resources to perform updates or installing any packages. By default, each TemplateVM has *2 VCPUs* for *4000 MB Max memory* allocated. If needed, double those values, *4 VCPUs* for *8000 MB Max memory*. For example, it has been observed failing updates or builds with *4 VCPUs* for *4000 MB Max memory* due to out of memory issue. For more general considerations, we refer to the official [Gentoo Handbook].
|
||||
|
||||
## Want to contribute?
|
||||
|
||||
* [How can I contribute to the Qubes Project?](/doc/contributing/)
|
||||
* [How can I contribute to the Qubes Project?](https://www.qubes-os.org/doc/contributing/)
|
||||
|
||||
* [Guidelines for Documentation Contributors](/doc/doc-guidelines/)
|
||||
* [Guidelines for Documentation Contributors](https://www.qubes-os.org/doc/doc-guidelines/)
|
||||
|
||||
[switch]: /doc/templates/#switching
|
||||
[reinstall]: /doc/reinstall-template/
|
||||
[uninstall]: /doc/templates/#uninstalling
|
||||
[Minimal TemplateVMs]: /doc/templates/minimal/
|
||||
[Xfce TemplateVMs]: /doc/templates/xfce/
|
||||
[switch]: https://www.qubes-os.org/doc/templates/#switching
|
||||
[reinstall]: https://www.qubes-os.org/doc/reinstall-template/
|
||||
[uninstall]: https://www.qubes-os.org/doc/templates/#uninstalling
|
||||
[Minimal TemplateVMs]: https://www.qubes-os.org/doc/templates/minimal/
|
||||
[Xfce TemplateVMs]: https://www.qubes-os.org/doc/templates/xfce/
|
||||
[Gentoo Handbook]: https://wiki.gentoo.org/wiki/Handbook:AMD64
|
||||
|
|
@ -14,7 +14,7 @@ Tips for Linux in HVM domain
|
|||
How to fix bootup kernel error
|
||||
-------------------------------
|
||||
|
||||
If the HVM pauses on boot and shows a series of warnings, visit [HVM Troubleshooting](/doc/hvm-troubleshooting/#hvm-pauses-on-boot-followed-by-kernel-error) for a fix.
|
||||
If the HVM pauses on boot and shows a series of warnings, visit [HVM Troubleshooting](https://www.qubes-os.org/doc/hvm-troubleshooting/#hvm-pauses-on-boot-followed-by-kernel-error) for a fix.
|
||||
|
||||
Screen resolution
|
||||
-----------------
|
||||
|
|
|
|||
|
|
@ -20,9 +20,9 @@ Penetration Testing Distributions
|
|||
|
||||
The following instructions explain how to install a penetration testing distribution within Qubes OS.
|
||||
|
||||
- [BlackArch](/doc/pentesting/blackarch/)
|
||||
- [Kali](/doc/pentesting/kali/)
|
||||
- [PenTester Framework (PTF)](/doc/pentesting/ptf/)
|
||||
- [BlackArch](https://www.qubes-os.org/doc/pentesting/blackarch/)
|
||||
- [Kali](https://www.qubes-os.org/doc/pentesting/kali/)
|
||||
- [PenTester Framework (PTF)](https://www.qubes-os.org/doc/pentesting/ptf/)
|
||||
|
||||
Using Qubes OS to host a "hacking" laboratory
|
||||
---------------------------------------------
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Create ArchLinux Based BlackArch Template
|
|||
|
||||
1. Create ArchlLinux Template
|
||||
|
||||
- Follow the [Archlinux Template instructions](/doc/building-archlinux-template/)
|
||||
- Follow the [Archlinux Template instructions](https://www.qubes-os.org/doc/building-archlinux-template/)
|
||||
|
||||
|
||||
2. Update Template
|
||||
|
|
@ -91,6 +91,6 @@ Create ArchLinux Based BlackArch Template
|
|||
Alternative Options to BlackArch
|
||||
--------------------------------
|
||||
|
||||
- [Kali](/doc/pentesting/kali/)
|
||||
- [PenTester Framework (PTF)](/doc/pentesting/ptf/)
|
||||
- [Pentesting](/doc/pentesting/)
|
||||
- [Kali](https://www.qubes-os.org/doc/pentesting/kali/)
|
||||
- [PenTester Framework (PTF)](https://www.qubes-os.org/doc/pentesting/ptf/)
|
||||
- [Pentesting](https://www.qubes-os.org/doc/pentesting/)
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ From a Debian template <a name="templatevm-from-debian4_0"/>
|
|||
This is the recommended method.
|
||||
Easier to maintain and less demanding on resources, but you won’t have the full Kali GUI.
|
||||
|
||||
If you need to install custom kernel modules (wifi drivers, …) you need to use the kernel provided by Kali instead of the kernel provided by Qubes, see [Managing VM Kernel.](/doc/managing-vm-kernel/)
|
||||
If you need to install custom kernel modules (wifi drivers, …) you need to use the kernel provided by Kali instead of the kernel provided by Qubes, see [Managing VM Kernel.](https://www.qubes-os.org/doc/managing-vm-kernel/)
|
||||
|
||||
The steps can be summarized as:
|
||||
|
||||
|
|
@ -162,13 +162,13 @@ Notes
|
|||
=============
|
||||
Thanks to the people in [the discussion thread](https://github.com/QubesOS/qubes-issues/issues/1981).
|
||||
|
||||
[qubes-verifying-signatures]: /security/verifying-signatures/
|
||||
[qubes-pentesting]: /doc/pentesting/
|
||||
[qubes-blackarch]: /doc/pentesting/blackarch/
|
||||
[qubes-ptf]: /doc/pentesting/ptf/
|
||||
[qubes-template-debian-install]: /doc/templates/debian/#install
|
||||
[qubes-resize-disk-image]: /doc/resize-disk-image/
|
||||
[qubes-new-hvm]: /doc/standalone-and-hvm/
|
||||
[qubes-verifying-signatures]: https://www.qubes-os.org/security/verifying-signatures/
|
||||
[qubes-pentesting]: https://www.qubes-os.org/doc/pentesting/
|
||||
[qubes-blackarch]: https://www.qubes-os.org/doc/pentesting/blackarch/
|
||||
[qubes-ptf]: https://www.qubes-os.org/doc/pentesting/ptf/
|
||||
[qubes-template-debian-install]: https://www.qubes-os.org/doc/templates/debian/#install
|
||||
[qubes-resize-disk-image]: https://www.qubes-os.org/doc/resize-disk-image/
|
||||
[qubes-new-hvm]: https://www.qubes-os.org/doc/standalone-and-hvm/
|
||||
|
||||
[kali]: https://www.kali.org/
|
||||
[kali-vbox]: https://www.offensive-security.com/kali-linux-vmware-virtualbox-image-download/
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ Create Debian Based Penetration Testers Framework (PTF) Template
|
|||
|
||||
1. Create PTF template
|
||||
|
||||
1. Follow [Create Debian Based Kali Template](/doc/pentesting/kali/) till step 7.
|
||||
1. Follow [Create Debian Based Kali Template](https://www.qubes-os.org/doc/pentesting/kali/) till step 7.
|
||||
|
||||
2. (Optional) Rename the cloned template to `ptf`
|
||||
|
||||
|
|
@ -68,7 +68,7 @@ possible to do sudo ptf/ptf
|
|||
|
||||
sudo ptf
|
||||
|
||||
|
||||
|
||||
|
||||
2. Show available modules (tools)
|
||||
|
||||
|
|
@ -116,6 +116,6 @@ possible to do sudo ptf/ptf
|
|||
Alternative Options to PTF
|
||||
--------------------------
|
||||
|
||||
- [BlackArch](/doc/pentesting/blackarch/)
|
||||
- [Kali](/doc/pentesting/kali/)
|
||||
- [Pentesting](/doc/pentesting/)
|
||||
- [BlackArch](https://www.qubes-os.org/doc/pentesting/blackarch/)
|
||||
- [Kali](https://www.qubes-os.org/doc/pentesting/kali/)
|
||||
- [Pentesting](https://www.qubes-os.org/doc/pentesting/)
|
||||
|
|
|
|||
|
|
@ -58,5 +58,5 @@ If you want to help in improving the template, feel free to [contribute][contrib
|
|||
|
||||
[IP]: https://www.ubuntu.com/legal/terms-and-policies/intellectual-property-policy
|
||||
[repo]: https://github.com/QubesOS/qubes-builder/blob/master/README.md
|
||||
[builder]: /doc/qubes-builder/
|
||||
[contrib]: /doc/contributing/
|
||||
[builder]: https://www.qubes-os.org/doc/qubes-builder/
|
||||
[contrib]: https://www.qubes-os.org/doc/contributing/
|
||||
|
|
|
|||
|
|
@ -20,8 +20,8 @@ Qubes Windows Tools
|
|||
Qubes Windows Tools are a set of programs and drivers that provide integration of Windows AppVMs with the rest of the Qubes system. Currently the following features are available for Windows VMs after installation of those tools:
|
||||
|
||||
- **Qubes Video Driver** - provides for the Seamless GUI mode that integrates apps windows onto the common Qubes trusted desktop
|
||||
- **File sender/receiver** - Support for [secure clipboard copy/paste](/doc/copy-paste/) between the Windows VM and other AppVMs
|
||||
- ***File sender/receiver** - Support for [secure file exchange](/doc/copying-files/) between the Windows VM and other AppVMs
|
||||
- **File sender/receiver** - Support for [secure clipboard copy/paste](https://www.qubes-os.org/doc/copy-paste/) between the Windows VM and other AppVMs
|
||||
- ***File sender/receiver** - Support for [secure file exchange](https://www.qubes-os.org/doc/copying-files/) between the Windows VM and other AppVMs
|
||||
- **Copy/Edit in Disposable VM** - Support for editing files in DisposableVMs as well as for qvm-run and generic qrexec for the Windows VM (e.g. ability to run custom service within/from the Windows VM)
|
||||
- **Xen PV drivers** for Windows that increase performance compared to qemu emulated devices
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ NOTES:
|
|||
Installing Windows OS in a Qubes VM
|
||||
-----------------------------------
|
||||
|
||||
Please refer to [this page](/doc/windows-vm/) for instructions on how to install Windows in a Qubes VM.
|
||||
Please refer to [this page](https://www.qubes-os.org/doc/windows-vm/) for instructions on how to install Windows in a Qubes VM.
|
||||
|
||||
NOTE: It is strongly suggested to enable autologon for any Windows HVMs that will have Qubes Tools installed. To do so, run `netplwiz` command from the `Win+R`/Start menu and uncheck the *Users must enter a user name and password to use this computer* option.
|
||||
|
||||
|
|
@ -184,7 +184,7 @@ Once you start a Windows-based AppVM with Qubes Tools installed, you can easily
|
|||
qvm-run -a my-win7-appvm explorer.exe
|
||||
~~~
|
||||
|
||||
 
|
||||
 
|
||||
|
||||
Also, the inter-VM services work as usual -- e.g. to request opening a document or URL in the Windows AppVM from another VM:
|
||||
|
||||
|
|
@ -202,7 +202,7 @@ Inter-VM file copy and clipboard works for Windows AppVMs the same way as for Li
|
|||
|
||||
To simulate CTRL-ALT-DELETE in the HVM (SAS, Secure Attention Sequence), press Ctrl-Alt-Home while having any window of this VM in the foreground.
|
||||
|
||||
|
||||
|
||||
|
||||
Changing between seamless and full desktop mode
|
||||
-----------------------------------------------
|
||||
|
|
@ -220,7 +220,7 @@ In order to create a HVM TemplateVM one can use the following command, suitably
|
|||
qvm-create --class TemplateVM win-template --property virt_mode=HVM --property kernel='' -l green
|
||||
~~~
|
||||
|
||||
... , set memory as appropriate, and install Windows OS (or other OS) into this template the same way as you would install it into a normal HVM -- please see instructions on [this page](/doc/hvm-create/).
|
||||
... , set memory as appropriate, and install Windows OS (or other OS) into this template the same way as you would install it into a normal HVM -- please see instructions on [this page](https://www.qubes-os.org/doc/hvm-create/).
|
||||
|
||||
If you use this Template as it is, then any HVMs that use it will effectively be DisposableVMs - the User directory will be wiped when the HVN is closed down.
|
||||
|
||||
|
|
@ -303,7 +303,7 @@ Debug and Verbose levels can generate large volume of logs and are intended for
|
|||
|
||||
To override global settings for a specific component, create a new key under the root key mentioned above and name it as the executable name, without `.exe` extension. For example, to change qrexec-agent's log level to Debug, set it like this:
|
||||
|
||||
|
||||
|
||||
|
||||
Component-specific settings currently available:
|
||||
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@ qvm-prefs win7new qrexec_timeout 300
|
|||
qvm-prefs win7new debug false
|
||||
~~~
|
||||
|
||||
To install Qubes Windows Tools, follow instructions in [Qubes Windows Tools](/doc/windows-tools/).
|
||||
To install Qubes Windows Tools, follow instructions in [Qubes Windows Tools](https://www.qubes-os.org/doc/windows-tools/).
|
||||
|
||||
### Detailed instructions ###
|
||||
|
||||
|
|
@ -119,9 +119,9 @@ MS Windows versions considerations:
|
|||
|
||||
- The instructions *may* work on other versions than Windows 7 x64 but haven't been tested.
|
||||
- Qubes Windows Tools (QWT) only supports Windows 7 x64. Note that there are [known issues](https://github.com/QubesOS/qubes-issues/issues/3585) with QWT on Qubes 4.x
|
||||
- For Windows 10 under Qubes 4.0, a way to install QWT 4.0.1.3, which has worked in several instances, is described in [Qubes Windows Tools](/doc/windows-tools/).
|
||||
- For Windows 10 under Qubes 4.0, a way to install QWT 4.0.1.3, which has worked in several instances, is described in [Qubes Windows Tools](https://www.qubes-os.org/doc/windows-tools/).
|
||||
|
||||
Create a VM named win7new in [HVM](/doc/hvm/) mode (Xen's current PVH limitations precludes from using PVH):
|
||||
Create a VM named win7new in [HVM](https://www.qubes-os.org/doc/hvm/) mode (Xen's current PVH limitations precludes from using PVH):
|
||||
|
||||
~~~
|
||||
qvm-create --class StandaloneVM --label red --property virt_mode=hvm win7new
|
||||
|
|
@ -170,7 +170,7 @@ To avoid that error we temporarily have to switch the video adapter to 'cirrus':
|
|||
qvm-features win7new video-model cirrus
|
||||
~~~
|
||||
|
||||
The VM is now ready to be started; the best practice is to use an installation ISO [located in a VM](/doc/standalone-and-hvm/#installing-an-os-in-an-hvm):
|
||||
The VM is now ready to be started; the best practice is to use an installation ISO [located in a VM](https://www.qubes-os.org/doc/standalone-and-hvm/#installing-an-os-in-an-hvm):
|
||||
|
||||
~~~
|
||||
qvm-start --cdrom=untrusted:/home/user/windows_install.iso win7new
|
||||
|
|
@ -209,7 +209,7 @@ Finally, increase the VM's `qrexec_timeout`: in case you happen to get a BSOD or
|
|||
qvm-prefs win7new qrexec_timeout 300
|
||||
~~~
|
||||
|
||||
At that point you should have a functional and stable Windows VM, although without updates, Xen's PV drivers nor Qubes integration (see sections [Windows Update](#windows-update) and [Xen PV drivers and Qubes Windows Tools](/doc/windows-tools/#xen-pv-drivers-and-qubes-windows-tools)). It is a good time to clone the VM again.
|
||||
At that point you should have a functional and stable Windows VM, although without updates, Xen's PV drivers nor Qubes integration (see sections [Windows Update](#windows-update) and [Xen PV drivers and Qubes Windows Tools](https://www.qubes-os.org/doc/windows-tools/#xen-pv-drivers-and-qubes-windows-tools)). It is a good time to clone the VM again.
|
||||
|
||||
|
||||
Windows as TemplateVM
|
||||
|
|
@ -254,5 +254,5 @@ To avoid guessing the VM's state enable debugging (`qvm-prefs -s win7new debug t
|
|||
Further customization
|
||||
---------------------
|
||||
|
||||
Please see the [Customizing Windows 7 templates](/doc/windows-template-customization/) page (despite the focus on preparing the VM for use as a template, most of the instructions are independent from how the VM will be used - ie. TemplateVM or StandaloneVM).
|
||||
Please see the [Customizing Windows 7 templates](https://www.qubes-os.org/doc/windows-template-customization/) page (despite the focus on preparing the VM for use as a template, most of the instructions are independent from how the VM will be used - ie. TemplateVM or StandaloneVM).
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue