aboutsummaryrefslogtreecommitdiff
path: root/docs/gnulinux
diff options
context:
space:
mode:
Diffstat (limited to 'docs/gnulinux')
-rw-r--r--docs/gnulinux/configuring_parabola.md228
-rw-r--r--docs/gnulinux/encrypted_debian.md13
-rw-r--r--docs/gnulinux/encrypted_parabola.md352
-rw-r--r--docs/gnulinux/grub_boot_installer.md59
-rw-r--r--docs/gnulinux/grub_cbfs.md49
-rw-r--r--docs/gnulinux/grub_hardening.md5
-rw-r--r--docs/gnulinux/index.md1
7 files changed, 414 insertions, 293 deletions
diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md
index 9d167bce..0c35eacd 100644
--- a/docs/gnulinux/configuring_parabola.md
+++ b/docs/gnulinux/configuring_parabola.md
@@ -19,6 +19,7 @@ Table of Contents
- [Pacman command equivalents (compared to other package
managers)](#pacman_commandequiv)
- [your-freedom](#yourfreedom)
+
- [Add a user account](#useradd)
- [System D](#systemd)
- [Interesting repositories](#interesting_repos)
@@ -94,10 +95,10 @@ careful about this when reading anything on the Arch wiki.
Some of these steps require internet access. I'll go into networking
-later but for now, I just connected my system to a switch and did:\
-\# **systemctl start dhcpcd.service**\
-You can stop it later by running:\
-\# **systemctl stop dhcpcd.service**\
+later but for now, I just connected my system to a switch and did:
+ # systemctl start dhcpcd.service
+You can stop it later by running:
+ # systemctl stop dhcpcd.service\
For most people this should be enough, but if you don't have DHCP on
your network then you should setup your network connection first:\
[Setup network connection in Parabola](#network)
@@ -126,13 +127,15 @@ Updating Parabola {#pacman_update}
-----------------
In the end, I didn't change my configuration for pacman. When you are
-updating, resync with the latest package names/versions:\
-\# **pacman -Syy**\
+updating, resync with the latest package names/versions:
+
+ # pacman -Syy
(according to the wiki, -Syy is better than Sy because it refreshes the
package list even if it appears to be up to date, which can be useful
when switching to another mirror).\
-Then, update the system:\
-\# **pacman -Syu**
+Then, update the system:
+
+ # pacman -Syu
**Before installing packages with 'pacman -S', always update first,
using the notes above.**
@@ -196,8 +199,9 @@ once in a while, to prevent it from growing too big (it's a cache of
old package information, updated automatically when you do anything in
pacman).**
-To clean out all old packages that are cached:\
-\# **pacman -Sc**
+To clean out all old packages that are cached:
+
+ # pacman -Sc
The wiki cautions that this should be used with care. For example, since
older packages are deleted from the repo, if you encounter issues and
@@ -205,8 +209,9 @@ want to revert back to an older package then it's useful to have the
caches available. Only do this if you are sure that you won't need it.
The wiki also mentions this method for removing everything from the
-cache, including currently installed packages that are cached:\
-\# **pacman -Scc**\
+cache, including currently installed packages that are cached:
+
+ # pacman -Scc
This is inadvisable, since it means re-downloading the package again if
you wanted to quickly re-install it. This should only be used when disk
space is at a premium.
@@ -251,10 +256,12 @@ access to the entire operating system.
Read the entire document linked to above, and then continue.
-Add your user:\
-\# **useradd -m -G wheel -s /bin/bash *yourusername***\
-Set a password:\
-\# **passwd *yourusername***
+Add your user:
+
+ # useradd -m -G wheel -s /bin/bash *yourusername*
+Set a password:
+
+ # passwd *yourusername*
Use of the *diceware method* is recommended, for generating secure
passphrases (instead of passwords).
@@ -280,8 +287,9 @@ sshd (openssh), dhcp, etc. There are countless others.
the background behind the decision by Arch (Parabola's upstream
supplier) to use systemd.
-The manpage should also help:\
-\# **man systemd**\
+The manpage should also help:
+
+ # man systemd
The section on 'unit types' is especially useful.
According to the wiki, systemd 'journal' keeps logs of a size up to
@@ -300,8 +308,9 @@ The wiki also recommended a method for forwarding journal output to TTY
12 (accessible by pressing ctrl+alt+f12, and you use ctrl+alt+\[F1-F12\]
to switch between terminals). I decided not to enable it.
-Restart journald:\
-\# **systemctl restart systemd-journald**
+Restart journald:
+
+ # systemctl restart systemd-journald
The wiki recommends that if the journal gets too large, you can also
simply delete (rm -Rf) everything inside /var/log/journald/\* but
@@ -311,10 +320,12 @@ delete older records when the journal size reaches it's limit
(according to systemd developers).
Finally, the wiki mentions 'temporary' files and the utility for
-managing them.\
-\# **man systemd-tmpfiles**\
-The command for 'clean' is:\
-\# **systemd-tmpfiles \--clean**\
+managing them.
+
+ # man systemd-tmpfiles
+The command for 'clean' is:
+
+ # systemd-tmpfiles --clean
According to the manpage, this *"cleans all files and directories with
an age parameter"*. According to the Arch wiki, this reads information
in /etc/tmpfiles.d/ and /usr/lib/tmpfiles.d/ to know what actions to
@@ -323,8 +334,9 @@ locations to get a better understanding.
I looked in /etc/tmpfiles.d/ and found that it was empty on my system.
However, /usr/lib/tmpfiles.d/ contained some files. The first one was
-etc.conf, containing information and a reference to this manpage:\
-\# **man tmpfiles.d**\
+etc.conf, containing information and a reference to this manpage:
+
+ # man tmpfiles.d
Read that manpage, and then continue studying all the files.
The systemd developers tell me that it isn't usually necessary to touch
@@ -348,11 +360,13 @@ and below the 'extra' section add:\
*\[kernels\]\
Include = /etc/pacman.d/mirrorlist*
-Now sync with the repository:\
-\# **pacman -Syy**
+Now sync with the repository:
+
+ # pacman -Syy
+
+List all available packages in this repository:
-List all available packages in this repository:\
-\# **pacman -Sl kernels**
+ # pacman -Sl kernels
In the end, I decided not to install anything from it but I kept the
repository enabled regardless.
@@ -372,13 +386,15 @@ Read <https://wiki.archlinux.org/index.php/Configuring_Network>.
This should be the same as the hostname that you set in /etc/hostname
when installing Parabola. You can also do it with systemd (do so now, if
-you like):\
-\# **hostnamectl set-hostname *yourhostname***\
+you like):
+
+ # hostnamectl set-hostname *yourhostname*
This writes the specified hostname to /etc/hostname. More information
-can be found in these manpages:\
-\# **man hostname**\
-\# **info hostname**\
-\# **man hostnamectl**
+can be found in these manpages:
+
+ # man hostname
+ # info hostname
+ # man hostnamectl
Add the same hostname to /etc/hosts, on each line. Example:\
*127.0.0.1 localhost.localdomain localhost myhostname\
@@ -399,8 +415,9 @@ According to the Arch wiki,
[udev](https://wiki.archlinux.org/index.php/Udev) should already detect
the ethernet chipset and load the driver for it automatically at boot
time. You can check this in the *"Ethernet controller"* section when
-running this command:\
-\# **lspci -v**
+running this command:
+
+ # lspci -v
Look at the remaining sections *'Kernel driver in use'* and *'Kernel
modules'*. In my case it was as follows:\
@@ -408,8 +425,9 @@ modules'*. In my case it was as follows:\
Kernel modules: e1000e*
Check that the driver was loaded by issuing *dmesg | grep module\_name*.
-In my case, I did:\
-\# **dmesg | grep e1000e**
+In my case, I did:
+
+ # dmesg | grep e1000e
### Network device names {#network_devicenames}
@@ -430,8 +448,9 @@ instructions in [grub\_cbfs.html](grub_cbfs.html)).
For background information, read [Predictable Network Interface
Names](http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/)
-Show device names:\
-\# **ls /sys/class/net**
+Show device names:
+
+ # ls /sys/class/net
Changing the device names is possible (I chose not to do it):\
<https://wiki.archlinux.org/index.php/Configuring_Network#Change_device_name>
@@ -462,8 +481,9 @@ is important, so make sure to read them!**
Install smartmontools (it can be used to check smart data. HDDs use
non-free firmware inside, but it's transparent to you but the smart
-data comes from it. Therefore, don't rely on it too much):\
-\# **pacman -S smartmontools**\
+data comes from it. Therefore, don't rely on it too much):
+
+ # pacman -S smartmontools
Read <https://wiki.archlinux.org/index.php/S.M.A.R.T.> to learn how to
use it.
@@ -487,28 +507,34 @@ provide LXDE by default.
Based on <https://wiki.archlinux.org/index.php/Xorg>.
-Firstly, install it!\
-\# **pacman -S xorg-server**\
+Firstly, install it!
+
+ # pacman -S xorg-server
I also recommend installing this (contains lots of useful tools,
-including *xrandr*):\
-\# **pacman -S xorg-server-utils**
+including *xrandr*):
+
+ # pacman -S xorg-server-utils
Install the driver. For me this was *xf86-video-intel* on the ThinkPad
-X60. T60 and macbook11/21 should be the same.\
-\# **pacman -S xf86-video-intel**\
-For other systems you can try:\
-\# **pacman -Ss xf86-video- | less**\
+X60. T60 and macbook11/21 should be the same.
+
+ # pacman -S xf86-video-intel
+For other systems you can try:
+
+ # pacman -Ss xf86-video- | less
Combined with looking at your *lspci* output, you can determine which
driver is needed. By default, Xorg will revert to xf86-video-vesa which
is a generic driver and doesn't provide true hardware acceleration.
Other drivers (not just video) can be found by looking at the
-*xorg-drivers* group:\
-\# **pacman -Sg xorg-drivers**\
+*xorg-drivers* group:
+
+ # pacman -Sg xorg-drivers
Mostly you will rely on a display manager, but in case you ever want to
-start X without one:\
-\# **pacman -S xorg-xinit**
+start X without one:
+
+ # pacman -S xorg-xinit
<optional>\
   Arch wiki recommends installing these, for testing that X works:\
@@ -535,8 +561,9 @@ will notice that the layout you set in /etc/vconsole.conf earlier might
not actually be the same in X.
To see what layout you currently use, try this on a terminal emulator in
-X:\
-\# **setxkbmap -print -verbose 10**
+X:
+
+ # setxkbmap -print -verbose 10
In my case, I wanted to use the Dvorak (UK) keyboard which is quite
different from Xorg's default Qwerty (US) layout.
@@ -582,36 +609,43 @@ would like to try something different, refer to
Refer to <https://wiki.archlinux.org/index.php/LXDE>.
-Install it, choosing 'all' when asked for the default package list:\
-\# **pacman -S lxde obconf**
+Install it, choosing 'all' when asked for the default package list:
-I didn't want the following, so I removed them:\
-\# **pacman -R lxmusic lxtask**
+ # pacman -S lxde obconf
-I also lazily installed all fonts:\
-\# **pacman -S \$(pacman -Ssq ttf-)**
+I didn't want the following, so I removed them:
-And a mail client:\
-\# **pacman -S icedove**
+ # pacman -R lxmusic lxtask
+
+I also lazily installed all fonts:
+
+ # pacman -S \$(pacman -Ssq ttf-)
+
+And a mail client:
+
+ # pacman -S icedove
In IceCat, go to *Preferences :: Advanced* and disable *GNU IceCat
Health Report*.
-I also like to install these:\
-\# **pacman -S xsensors stress htop**
+I also like to install these:
+
+ # pacman -S xsensors stress htop
-Enable LXDM (the default display manager, providing a graphical login):\
-\# **systemctl enable lxdm.service**\
-It will start when you boot up the system. To start it now, do:\
-\# **systemctl start lxdm.service**
+Enable LXDM (the default display manager, providing a graphical login):
+
+ # systemctl enable lxdm.service
+It will start when you boot up the system. To start it now, do:
+
+ # systemctl start lxdm.service
Log in with your standard (non-root) user that you created earlier. It
is advisable to also create an xinitrc rule in case you ever want to
start lxde without lxdm. Read
<https://wiki.archlinux.org/index.php/Xinitrc>.
-Open LXterminal:\
-\$ **cp /etc/skel/.xinitrc \~**\
+Open LXterminal:
+ $ cp /etc/skel/.xinitrc \~
Open .xinitrc and add the following plus a line break at the bottom of
the file.\
*\# Probably not needed. The same locale info that we set before\
@@ -621,8 +655,8 @@ export LANG=en\_GB.UTF-8\
\
\# Start lxde desktop\
exec startlxde\
-* Now make sure that it is executable:\
-\$ **chmod +x .xinitrc**
+* Now make sure that it is executable:
+ $ chmod +x .xinitrc
[Back to top of page.](#pagetop)
@@ -647,8 +681,9 @@ NOTE TO SELF: come back to this later.
### LXDE - screenlock {#lxde_screenlock}
-Arch wiki recommends to use *xscreensaver*:\
-\# **pacman -S xscreensaver**
+Arch wiki recommends to use *xscreensaver*:
+
+ # pacman -S xscreensaver
Under *Preferences :: Screensaver* in the LXDE menu, I chose *Mode:
Blank Screen Only*, setting *Blank After*, *Cycle After* and *Lock
@@ -698,31 +733,38 @@ cursor over it, it'll show information about the battery.
Refer to <https://wiki.archlinux.org/index.php/LXDE#Network_Management>.
Then I read: <https://wiki.archlinux.org/index.php/NetworkManager>.
-Install Network Manager:\
-\# **pacman -S networkmanager**
+Install Network Manager:
+
+ # pacman -S networkmanager
+
+You will also want the graphical applet:
-You will also want the graphical applet:\
-\# **pacman -S network-manager-applet**\
+ # pacman -S network-manager-applet
Arch wiki says that an autostart rule will be written at
*/etc/xdg/autostart/nm-applet.desktop*
I want to be able to use a VPN at some point, so the wiki tells me to
-do:\
-\# **pacman -S networkmanager-openvpn**
+do:
+
+ # pacman -S networkmanager-openvpn
LXDE uses openbox, so I refer to:\
<https://wiki.archlinux.org/index.php/NetworkManager#Openbox>.
-It tells me for the applet I need:\
-\# **pacman -S xfce4-notifyd gnome-icon-theme**\
-Also, for storing authentication details (wifi) I need:\
-\# **pacman -S gnome-keyring**
+It tells me for the applet I need:
+
+ # pacman -S xfce4-notifyd gnome-icon-theme
+Also, for storing authentication details (wifi) I need:
+
+ # pacman -S gnome-keyring
+
+I wanted to quickly enable networkmanager:
+
+ # systemctl stop dhcpcd
+ # systemctl start NetworkManager
+Enable NetworkManager at boot time:
-I wanted to quickly enable networkmanager:\
-\# **systemctl stop dhcpcd**\
-\# **systemctl start NetworkManager**\
-Enable NetworkManager at boot time:\
-\# **systemctl enable NetworkManager**
+ # systemctl enable NetworkManager
Restart LXDE (log out, and then log back in).
diff --git a/docs/gnulinux/encrypted_debian.md b/docs/gnulinux/encrypted_debian.md
index b0f0b586..6d964b9c 100644
--- a/docs/gnulinux/encrypted_debian.md
+++ b/docs/gnulinux/encrypted_debian.md
@@ -77,6 +77,7 @@ Choose 'Manual' partitioning:
- Encryption key: passphrase
- erase data: Yes (only choose 'No' if it's a new drive that
doesn't contain your private data)
+
- Select 'configure encrypted volumes'
- Create encrypted volumes
- Select your partition
@@ -185,12 +186,12 @@ At this point, you will have finished the installation. At your GRUB
payload, press C to get to the command line.
Do that:\
-grub> **cryptomount -a**\
-grub> **set root='lvm/matrix-rootvol'**\
+ grub> cryptomount -a
+ grub> set root='lvm/matrix-rootvol'\
grub> **linux /vmlinuz root=/dev/mapper/matrix-rootvol
cryptdevice=/dev/mapper/matrix-rootvol:root**\
-grub> **initrd /initrd.img**\
-grub> **boot**
+ grub> initrd /initrd.img
+ grub> boot
@@ -200,8 +201,8 @@ ecryptfs
If you didn't encrypt your home directory, then you can safely ignore
this section.
-Immediately after logging in, do that:\
-\$ **sudo ecryptfs-unwrap-passphrase**
+Immediately after logging in, do that:
+ $ sudo ecryptfs-unwrap-passphrase
This will be needed in the future if you ever need to recover your home
directory from another system, so write it down and keep the note
diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md
index 2ac5a5ec..af42525b 100644
--- a/docs/gnulinux/encrypted_parabola.md
+++ b/docs/gnulinux/encrypted_parabola.md
@@ -68,13 +68,14 @@ article](https://wiki.archlinux.org/index.php/Solid_State_Drives). Edit
/etc/fstab later on when chrooted into your install. Also, read the
whole article and keep all points in mind, adapting them for this guide.
-Securely wipe the drive:\
-\# **dd if=/dev/urandom of=/dev/sda; sync**\
+Securely wipe the drive:
+ # dd if=/dev/urandom of=/dev/sda; sync
+
NOTE: If you have an SSD, only do this the first time. If it was already
LUKS-encrypted before, use the info below to wipe the LUKS header. Also,
check online for your SSD what the recommended erase block size is. For
-example if it was 2MiB:\
-\# **dd if=/dev/urandom of=/dev/sda bs=2M; sync**
+example if it was 2MiB:
+ # dd if=/dev/urandom of=/dev/sda bs=2M; sync
If your drive was already LUKS encrypted (maybe you are re-installing
your distro) then it is already 'wiped'. You should just wipe the LUKS
@@ -82,8 +83,9 @@ header.
<https://www.lisenet.com/2013/luks-add-keys-backup-and-restore-volume-header/>
showed me how to do this. It recommends doing the first 3MiB. Now, that
guide is recommending putting zero there. I'm going to use urandom. Do
-this:\
-\# **head -c 3145728 /dev/urandom > /dev/sda; sync**\
+this:
+
+ # head -c 3145728 /dev/urandom > /dev/sda; sync
(Wiping the LUKS header is important, since it has hashed passphrases
and so on. It's 'secure', but 'potentially' a risk).
@@ -93,9 +95,10 @@ Change keyboard layout
----------------------
Parabola live shell assumes US Qwerty. If you have something different,
-list the available keymaps and use yours:\
-\# **localectl list-keymaps**\
-\# **loadkeys LAYOUT**\
+list the available keymaps and use yours:
+
+ # localectl list-keymaps
+ # loadkeys LAYOUT
For me, LAYOUT would have been dvorak-uk.
@@ -122,8 +125,9 @@ dm-mod
------
device-mapper will be used - a lot. Make sure that the kernel module is
-loaded:\
-\# **modprobe dm-mod**
+loaded:
+
+ # modprobe dm-mod
Create LUKS partition
---------------------
@@ -136,8 +140,9 @@ prepared cryptsetup command below. Note that the iteration time is for
security purposes (mitigates brute force attacks), so anything lower
than 5 seconds is probably not ok.
-I am using MBR partitioning, so I use cfdisk:\
-\# **cfdisk /dev/sda**
+I am using MBR partitioning, so I use cfdisk:
+
+ # cfdisk /dev/sda
I create a single large sda1 filling the whole drive, leaving it as the
default type 'Linux' (83).
@@ -149,16 +154,19 @@ I am then directed to
Parabola forces you to RTFM. Do that.
-It tells me to run:\
-\# **cryptsetup benchmark** (for making sure the list below is
+It tells me to run:
+
+ # cryptsetup benchmark (for making sure the list below is
populated)\
-Then:\
-\# **cat /proc/crypto**\
+Then:
+
+ # cat /proc/crypto
This gives me crypto options that I can use. It also provides a
representation of the best way to set up LUKS (in this case, security is
a priority; speed, a distant second). To gain a better understanding, I
-am also reading:\
-\# **man cryptsetup**
+am also reading:
+
+ # man cryptsetup
Following that page, based on my requirements, I do the following based
on
@@ -167,8 +175,8 @@ Reading through, it seems like Serpent (encryption) and Whirlpool (hash)
is the best option.
I am initializing LUKS with the following:\
-\# **cryptsetup -v \--cipher serpent-xts-plain64 \--key-size 512 \--hash
-whirlpool \--iter-time 500 \--use-random \--verify-passphrase luksFormat
+\# **cryptsetup -v --cipher serpent-xts-plain64 --key-size 512 --hash
+whirlpool --iter-time 500 --use-random --verify-passphrase luksFormat
/dev/sda1** Choose a **secure** passphrase here. Ideally lots of
lowercase/uppercase numbers, letters, symbols etc all in a random
pattern. The password length should be as long as you are able to handle
@@ -184,30 +192,37 @@ Create LVM
Now I refer to <https://wiki.archlinux.org/index.php/LVM>.
-Open the LUKS partition:\
-\# **cryptsetup luksOpen /dev/sda1 lvm**\
+Open the LUKS partition:
+
+ # cryptsetup luksOpen /dev/sda1 lvm
(it will be available at /dev/mapper/lvm)
-Create LVM partition:\
-\# **pvcreate /dev/mapper/lvm**\
-Show that you just created it:\
-\# **pvdisplay**
+Create LVM partition:
+
+ # pvcreate /dev/mapper/lvm
+Show that you just created it:
+
+ # pvdisplay
Now I create the volume group, inside of which the logical volumes will
-be created:\
-\# **vgcreate matrix /dev/mapper/lvm**\
+be created:
+
+ # vgcreate matrix /dev/mapper/lvm
(volume group name is 'matrix' - choose your own name, if you like)
-Show that you created it:\
-\# **vgdisplay**
+Show that you created it:
-Now create the logical volumes:\
-\# **lvcreate -L 2G matrix -n swapvol** (2G swap partition, named
+ # vgdisplay
+
+Now create the logical volumes:
+
+ # lvcreate -L 2G matrix -n swapvol (2G swap partition, named
swapvol)\
Again, choose your own name if you like. Also, make sure to choose a
swap size of your own needs. It basically depends on how much RAM you
have installed. I refer to
-<http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space>.\
-\# **lvcreate -l +100%FREE matrix -n root** (single large partition in
+<http://www.linux.com/news/software/applications/8208-all-about-linux-swap-space>.
+
+ # lvcreate -l +100%FREE matrix -n root (single large partition in
the rest of the space, named root)\
You can also be flexible here, for example you can specify a /boot, a /,
a /home, a /var, a /usr, etc. For example, if you will be running a
@@ -216,24 +231,29 @@ fills up with logs, it won't crash your system). For a home/laptop
system (typical use case), a root and a swap will do (really).
Verify that the logical volumes were created, using the following
-command:\
-\# **lvdisplay**
+command:
+
+ # lvdisplay
Create / and swap partitions, and mount
---------------------------------------
-For the swapvol LV I use:\
-\# **mkswap /dev/mapper/matrix-swapvol**\
-Activate swap:\
-\# **swapon /dev/matrix/swapvol**
+For the swapvol LV I use:
+
+ # mkswap /dev/mapper/matrix-swapvol
+Activate swap:
+
+ # swapon /dev/matrix/swapvol
+
+For the root LV I use:
-For the root LV I use:\
-\# **mkfs.btrfs /dev/mapper/matrix-root**
+ # mkfs.btrfs /dev/mapper/matrix-root
-Mount the root (/) partition:\
-\# **mount /dev/matrix/root /mnt**
+Mount the root (/) partition:
+
+ # mount /dev/matrix/root /mnt
@@ -247,19 +267,21 @@ Now I am following the rest of
<https://wiki.parabolagnulinux.org/Installation_Guide>. I also cross
referenced <https://wiki.archlinux.org/index.php/Installation_guide>.
-Create /home and /boot on root mountpoint:\
-\# **mkdir -p /mnt/home**\
-\# **mkdir -p /mnt/boot**
+Create /home and /boot on root mountpoint:
+
+ # mkdir -p /mnt/home
+ # mkdir -p /mnt/boot
Once all the remaining partitions, if any, have been mounted, the
devices are ready to install Parabola.
In **/etc/pacman.d/mirrorlist**, comment out all lines except the Server
line closest to where you are (I chose the UK Parabola server (main
-server)) and then did:\
-\# **pacman -Syy**\
-\# **pacman -Syu**\
-\# **pacman -Sy pacman** (and then I did the other 2 steps above,
+server)) and then did:
+
+ # pacman -Syy
+ # pacman -Syu
+ # pacman -Sy pacman (and then I did the other 2 steps above,
again)\
In my case I did the steps in the next paragraph, and followed the steps
in this paragraph again.
@@ -273,8 +295,8 @@ signing and verifying packages:\
   \# **pacman -Sy parabola-keyring**\
   It says that if you get GPG errors, then it's probably an expired
key and, therefore, you should do:\
-   \# **pacman-key \--populate parabola**\
-   \# **pacman-key \--refresh-keys**\
+   \# **pacman-key --populate parabola**\
+   \# **pacman-key --refresh-keys**\
   \# **pacman -Sy parabola-keyring**\
   To be honest, you should do the above anyway. Parabola has a lot of
maintainers, and a lot of keys. Really!\
@@ -286,7 +308,7 @@ manually set the correct time\
   \# **date MMDDhhmm\[\[CC\]YY\]\[.ss\]**\
   I also had to install:\
   \# **pacman -S archlinux-keyring**\
-   \# **pacman-key \--populate archlinux**\
+   \# **pacman-key --populate archlinux**\
   In my case I saw some conflicting files reported in pacman, stopping
me from using it.\
   I deleted the files that it mentioned and then it worked.
@@ -310,58 +332,71 @@ Configure the system
Generate an fstab - UUIDs are used because they have certain advantages
(see <https://wiki.parabola.nu/Fstab#Identifying_filesystems>. If you
-prefer labels instead, replace the -U option with -L):\
-\# **genfstab -U -p /mnt >> /mnt/etc/fstab**\
-Check the created file:\
-\# **cat /mnt/etc/fstab**\
+prefer labels instead, replace the -U option with -L):
+
+ # genfstab -U -p /mnt >> /mnt/etc/fstab
+Check the created file:
+
+ # cat /mnt/etc/fstab
(If there are any errors, edit the file. Do **NOT** run the genfstab
command again!)
-Chroot into new system:\
-\# **arch-chroot /mnt /bin/bash**
+Chroot into new system:
+
+ # arch-chroot /mnt /bin/bash
-It's a good idea to have this installed:\
-\# **pacman -S linux-libre-lts**
+It's a good idea to have this installed:
+
+ # pacman -S linux-libre-lts
It was also suggested that you should install this kernel (read up on
-what GRSEC is):\
-\# **pacman -S linux-libre-grsec**
+what GRSEC is):
+
+ # pacman -S linux-libre-grsec
This is another kernel that sits inside /boot, which you can use. LTS
means 'long-term support'. These are so-called 'stable' kernels that
can be used as a fallback during updates, if a bad kernel causes issues
for you.
-Parabola does not have wget. This is sinister. Install it:\
-\# **pacman -S wget**
+Parabola does not have wget. This is sinister. Install it:
-Locale:\
-\# **vi /etc/locale.gen**\
+ # pacman -S wget
+
+Locale:
+
+ # vi /etc/locale.gen
Uncomment your needed localisations. For example en\_GB.UTF-8 (UTF-8 is
-highly recommended over other options).\
-\# **locale-gen**\
-\# **echo LANG=en\_GB.UTF-8 > /etc/locale.conf**\
-\# **export LANG=en\_GB.UTF-8**
+highly recommended over other options).
+
+ # locale-gen
+ # echo LANG=en\_GB.UTF-8 > /etc/locale.conf
+ # export LANG=en\_GB.UTF-8
-Console font and keymap:\
-\# **vi /etc/vconsole.conf**\
+Console font and keymap:
+
+ # vi /etc/vconsole.conf
In my case:
KEYMAP=dvorak-uk
FONT=lat9w-16
-Time zone:\
-\# **ln -s /usr/share/zoneinfo/Europe/London /etc/localtime**\
+Time zone:
+
+ # ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
(Replace Zone and Subzone to your liking. See /usr/share/zoneinfo)
-Hardware clock:\
-\# **hwclock \--systohc \--utc**
+Hardware clock:
+
+ # hwclock --systohc --utc
Hostname: Write your hostname to /etc/hostname. For example, if your
-hostname is parabola:\
-\# **echo parabola > /etc/hostname**\
-Add the same hostname to /etc/hosts:\
-\# **vi /etc/hosts**\
+hostname is parabola:
+
+ # echo parabola > /etc/hostname
+Add the same hostname to /etc/hosts:
+
+ # vi /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost parabola
@@ -374,8 +409,9 @@ Mkinitcpio: Configure /etc/mkinitcpio.conf as needed (see
<https://wiki.parabola.nu/Mkinitcpio>). Runtime modules can be found in
/usr/lib/initcpio/hooks, and build hooks can be found in
/usr/lib/initcpio/install. (\# **mkinitcpio -H hookname** gives
-information about each hook.) Specifically, for this use case:\
-\# **vi /etc/mkinitcpio.conf**\
+information about each hook.) Specifically, for this use case:
+
+ # vi /etc/mkinitcpio.conf
Then modify the file like so:
- MODULES="i915"
@@ -399,19 +435,24 @@ Then modify the file like so:
Now using mkinitcpio, you can create the kernel and ramdisk for booting
with (this is different from Arch, specifying linux-libre instead of
-linux):\
-\# **mkinitcpio -p linux-libre**\
-Also do it for linux-libre-lts:\
-\# **mkinitcpio -p linux-libre-lts**\
-Also do it for linux-libre-grsec:\
-\# **mkinitcpio -p linux-libre-grsec**
+linux):
+
+ # mkinitcpio -p linux-libre
+Also do it for linux-libre-lts:
+
+ # mkinitcpio -p linux-libre-lts
+Also do it for linux-libre-grsec:
+
+ # mkinitcpio -p linux-libre-grsec
Set the root password: At the time of writing, Parabola used SHA512 by
default for its password hashing. I referred to
-<https://wiki.archlinux.org/index.php/SHA_password_hashes>.\
-\# **vi /etc/pam.d/passwd**\
-Add rounds=65536 at the end of the uncommented 'password' line.\
-\# **passwd root**\
+<https://wiki.archlinux.org/index.php/SHA_password_hashes>.
+
+ # vi /etc/pam.d/passwd
+Add rounds=65536 at the end of the uncommented 'password' line.
+
+ # passwd root
Make sure to set a secure password! Also, it must never be the same as
your LUKS password.
@@ -425,8 +466,9 @@ Extra security tweaks
Based on <https://wiki.archlinux.org/index.php/Security>.
-Restrict access to important directories:\
-\# **chmod 700 /boot /etc/{iptables,arptables}**
+Restrict access to important directories:
+
+ # chmod 700 /boot /etc/{iptables,arptables}
Lockout user after three failed login attempts:\
Edit the file /etc/pam.d/system-login and comment out that line:\
@@ -435,8 +477,9 @@ Or just delete it. Above it, put:\
*auth required pam\_tally.so deny=2 unlock\_time=600 onerr=succeed
file=/var/log/faillog*\
To unlock a user manually (if a password attempt is failed 3 times),
-do:\
-\# **pam\_tally \--user *theusername* \--reset** What the above
+do:
+
+ # pam\_tally --user *theusername* --reset What the above
configuration does is lock the user out for 10 minutes, if they make 3
failed login attempts.
@@ -449,21 +492,25 @@ don't really need sudo.
Unmount, reboot!
----------------
-Exit from chroot:\
-\# **exit**
+Exit from chroot:
+
+ # exit
+
+unmount:
-unmount:\
-\# **umount -R /mnt**\
-\# **swapoff -a**
+ # umount -R /mnt
+ # swapoff -a
-deactivate the lvm lv's:\
-\# **lvchange -an /dev/matrix/root**\
-\# **lvchange -an /dev/matrix/swapvol**\
+deactivate the lvm lv's:
-Lock the encrypted partition (close it):\
-\# **cryptsetup luksClose lvm**
+ # lvchange -an /dev/matrix/root
+ # lvchange -an /dev/matrix/swapvol
-\# **shutdown -h now**\
+Lock the encrypted partition (close it):
+
+ # cryptsetup luksClose lvm
+
+ # shutdown -h now
Remove the installation media, then boot up again.
@@ -475,12 +522,12 @@ Initially you will have to boot manually. Press C to get to the GRUB
command line. The underlined parts are optional (using those 2
underlines will boot lts kernel instead of normal).
-grub> **cryptomount -a**\
-grub> **set root='lvm/matrix-root'**\
+ grub> cryptomount -a
+ grub> set root='lvm/matrix-root'\
grub> **linux /boot/vmlinuz-linux-libre-lts root=/dev/matrix/root
cryptdevice=/dev/sda1:root**\
-grub> **initrd /boot/initramfs-linux-libre-lts.img**\
-grub> **boot**\
+ grub> initrd /boot/initramfs-linux-libre-lts.img
+ grub> boot\
You could also make it load /boot/vmlinuz-linux-libre-grsec and
/boot/initramfs-linux-libre-grsec.img
@@ -518,17 +565,19 @@ possibility of bricking your device!
I will go for the re-flash option here. Firstly, cd to the
libreboot\_util/cbfstool/{armv7l i686 x86\_64} directory. Dump the
current firmware - where *libreboot.rom* is an example: make sure to
-adapt:\
-\# **flashrom -p internal -r libreboot.rom**\
+adapt:
+
+ # flashrom -p internal -r libreboot.rom
If flashrom complains about multiple flash chips detected, add a *-c*
option at the end, with the name of your chosen chip is quotes.\
You can check if everything is in there (*grub.cfg* and *grubtest.cfg*
-would be really nice):\
-\$ **./cbfstool libreboot.rom print**\
-Extract grubtest.cfg:\
-\$ **./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**\
-And modify:\
-\$ **vi grubtest.cfg**
+would be really nice):
+ $ ./cbfstool libreboot.rom print
+Extract grubtest.cfg:
+ $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg\
+And modify:
+
+ $ vi grubtest.cfg
In grubtest.cfg, inside the 'Load Operating System' menu entry, change
the contents to:
@@ -556,19 +605,22 @@ detected LUKS volumes. You can also specify -u UUID or -a (device).
hardening your GRUB configuration, for security purposes.
Save your changes in grubtest.cfg, then delete the unmodified config
-from the ROM image:\
-\$ **./cbfstool libreboot.rom remove -n grubtest.cfg**\
+from the ROM image:
+
+ $ ./cbfstool libreboot.rom remove -n grubtest.cfg
and insert the modified grubtest.cfg:\
\$ **./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t
raw**\
Now refer to <http://libreboot.org/docs/install/#flashrom>. Cd (up) to
-the libreboot\_util directory and update the flash chip contents:\
-\# **./flash update libreboot.rom**\
+the libreboot\_util directory and update the flash chip contents:
+
+ # ./flash update libreboot.rom
Ocassionally, coreboot changes the name of a given board. If flashrom
complains about a board mismatch, but you are sure that you chose the
-correct ROM image, then run this alternative command:\
-\# **./flash forceupdate libreboot.rom**\
+correct ROM image, then run this alternative command:
+
+ # ./flash forceupdate libreboot.rom
You should see "Verifying flash\... VERIFIED." written at the end of
the flashrom output.
@@ -598,22 +650,26 @@ with the following command:\
\$ **sed -e 's:(cbfsdisk)/grub.cfg:(cbfsdisk)/grubtest.cfg:g' -e
's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg >
grub.cfg**\
-Delete the grub.cfg that remained inside the ROM:\
-\$ **./cbfstool libreboot.rom remove -n grub.cfg**\
-Add the modified version that you just made:\
-\$ **./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw**\
+Delete the grub.cfg that remained inside the ROM:
+
+ $ ./cbfstool libreboot.rom remove -n grub.cfg
+Add the modified version that you just made:
+
+ $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw
Now you have a modified ROM. Once more, refer to
<http://libreboot.org/docs/install/#flashrom>. Cd to the libreboot\_util
-directory and update the flash chip contents:\
-\# **./flash update libreboot.rom**\
+directory and update the flash chip contents:
+
+ # ./flash update libreboot.rom
And wait for the "Verifying flash\... VERIFIED." Once you have done
that, shut down and then boot up with your new configuration.
When done, delete GRUB (remember, we only needed it for the
*grub-mkpasswd-pbkdf2* utility; GRUB is already part of libreboot,
-flashed alongside it as a *payload*):\
-\# **pacman -R grub**
+flashed alongside it as a *payload*):
+
+ # pacman -R grub
@@ -637,18 +693,22 @@ putting a keyfile inside initramfs would be a bad idea).\
Boot up and login as root or your user. Then generate the key file:\
\# **dd bs=512 count=4 if=/dev/urandom of=/etc/mykeyfile
iflag=fullblock**\
-Insert it into the luks volume:\
-\# **cryptsetup luksAddKey /dev/sdX /etc/mykeyfile**\
+Insert it into the luks volume:
+
+ # cryptsetup luksAddKey /dev/sdX /etc/mykeyfile
and enter your LUKS passphrase when prompted. Add the keyfile to the
-initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example:\
-\# **FILES="/etc/mykeyfile"**\
-Create the initramfs image from scratch:\
-\# **mkinitcpio -p linux-libre**\
-\# **mkinitcpio -p linux-libre-lts**\
-\# **mkinitcpio -p linux-libre-grsec**\
+initramfs by adding it to FILES in /etc/mkinitcpio.conf. For example:
+
+ # FILES="/etc/mykeyfile"
+Create the initramfs image from scratch:
+
+ # mkinitcpio -p linux-libre
+ # mkinitcpio -p linux-libre-lts
+ # mkinitcpio -p linux-libre-grsec
Add the following to your grub.cfg - you are now able to do that, see
-above! -, or add it in the kernel command line for GRUB:\
-\# **cryptkey=rootfs:/etc/mykeyfile**\
+above! -, or add it in the kernel command line for GRUB:
+
+ # cryptkey=rootfs:/etc/mykeyfile
\
You can also place this inside the grub.cfg that exists in CBFS:
[grub\_cbfs.html](grub_cbfs.html).
diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md
index 08a1c83e..3275d5a4 100644
--- a/docs/gnulinux/grub_boot_installer.md
+++ b/docs/gnulinux/grub_boot_installer.md
@@ -28,20 +28,25 @@ Prepare the USB drive (in GNU+Linux)
If you downloaded your ISO on an existing GNU+Linux system, here is how
to create the bootable GNU+Linux USB drive:
-Connect the USB drive. Check dmesg:\
-**\$ dmesg**\
-Check lsblk to confirm which drive it is:\
-**\$ lsblk**
+Connect the USB drive. Check dmesg:
+
+ $ dmesg
+
+Check lsblk to confirm which drive it is:
+
+ $ lsblk
Check that it wasn't automatically mounted. If it was, unmount it. For
-example:\
-**\$ sudo umount /dev/sdX\***\
-**\# umount /dev/sdX\***
+example:
+
+ $ sudo umount /dev/sdX\*
+ # umount /dev/sdX\*
dmesg told you what device it is. Overwrite the drive, writing your
-distro ISO to it with dd. For example:\
-**\$ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync**\
-**\# dd if=gnulinux.iso of=/dev/sdX bs=8M; sync**
+distro ISO to it with dd. For example:
+
+ $ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync
+ # dd if=gnulinux.iso of=/dev/sdX bs=8M; sync
You should now be able to boot the installer from your USB drive.
Continue reading, for information about how to do that.
@@ -71,18 +76,22 @@ Prepare the USB drive (in LibertyBSD or OpenBSD)
If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is
how to create the bootable GNU+Linux USB drive:
-Connect the USB drive. Check dmesg:\
-**\$ dmesg | tail**\
-Check to confirm which drive it is, for example, if you think its sd3:\
-**\$ disklabel sd3**
+Connect the USB drive. Check dmesg:
+
+ $ dmesg | tail
+Check to confirm which drive it is, for example, if you think its sd3:
+
+ $ disklabel sd3
Check that it wasn't automatically mounted. If it was, unmount it. For
-example:\
-**\$ doas umount /dev/sd3i**\
+example:
+
+ $ doas umount /dev/sd3i
dmesg told you what device it is. Overwrite the drive, writing the
-OpenBSD installer to it with dd. For example:\
-**\$ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync**\
+OpenBSD installer to it with dd. For example:
+
+ $ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync
You should now be able to boot the installer from your USB drive.
Continue reading, for information about how to do that.
@@ -146,13 +155,13 @@ distribution it is that you are trying to install.*
If the ISOLINUX parser or *Search for GRUB configuration* options won't
work, then press C in GRUB to access the command line.\
-grub> **ls**\
+ grub> ls
Get the device from above output, eg (usb0). Example:\
-grub> **cat (usb0)/isolinux/isolinux.cfg**\
+ grub> cat (usb0)/isolinux/isolinux.cfg\
Either this will show the ISOLINUX menuentries for that ISO, or link to
other .cfg files, for example /isolinux/foo.cfg.\
If it did that, then you do:\
-grub> **cat (usb0)/isolinux/foo.cfg**\
+ grub> cat (usb0)/isolinux/foo.cfg
And so on, until you find the correct menuentries for ISOLINUX. **The
file */isolinux/foo.cfg* is a fictional example. Do not actually use
this example, unless you actually have that file, if it is
@@ -173,10 +182,10 @@ Now look at the ISOLINUX menuentry. It'll look like:\
append PARAMETERS initrd=/path/to/initrd MAYBE\_MORE\_PARAMETERS\
** GRUB works the same way, but in it's own way. Example GRUB
commands:\
-grub> **set root='usb0'**\
-grub> **linux /path/to/kernel PARAMETERS MAYBE\_MORE\_PARAMETERS**\
-grub> **initrd /path/to/initrd**\
-grub> **boot**\
+ grub> set root='usb0'\
+ grub> linux /path/to/kernel PARAMETERS MAYBE\_MORE\_PARAMETERS
+ grub> initrd /path/to/initrd
+ grub> boot
Note: *usb0* may be incorrect. Check the output of the *ls* command in
GRUB, to see a list of USB devices/partitions. Of course this will vary
from distro to distro. If you did all of that correctly, then it should
diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md
index 538a04fd..9809785f 100644
--- a/docs/gnulinux/grub_cbfs.md
+++ b/docs/gnulinux/grub_cbfs.md
@@ -45,6 +45,7 @@ Table of Contents
+
Introduction
------------
@@ -122,8 +123,8 @@ Acquire the necessary utilities {#tools}
Use ***cbfstool*** and ***flashrom***. There are available in the
*libreboot\_util* release archive, or they can be compiled (see
[../git/\#build\_flashrom](../git/#build_flashrom)). Flashrom is also
-available from the repositories:\
-\# **pacman -S flashrom**
+available from the repositories:
+ # pacman -S flashrom
[Back to top of page.](#pagetop)
@@ -138,12 +139,13 @@ flashed. For the purpose of this tutorial it is assumed that your ROM
image file is named *libreboot.rom*, so please make sure to adapt.
ROM images are included pre-compiled in libreboot. You can also dump
-your current firmware, using flashrom:\
-\$ **sudo flashrom -p internal -r libreboot.rom**\
-\# **flashrom -p internal -r libreboot.rom**\
+your current firmware, using flashrom:
+ $ sudo flashrom -p internal -r libreboot.rom
+ # flashrom -p internal -r libreboot.rom
If you are told to specify the chip, add the option **-c {your chip}**
-to the command, for example:\
-\# **flashrom -c MX25L6405 -p internal -r libreboot.rom**
+to the command, for example:
+
+ # flashrom -c MX25L6405 -p internal -r libreboot.rom
[Back to top of page.](#pagetop)
@@ -152,8 +154,9 @@ to the command, for example:\
Extract grubtest.cfg from the ROM image {#extract_testconfig}
---------------------------------------
-You can check the contents of the ROM image, inside CBFS:\
-**\$ cd \.../libreboot\_util/cbfstool** **\$ ./cbfstool libreboot.rom
+You can check the contents of the ROM image, inside CBFS:
+
+ $ cd \.../libreboot\_util/cbfstool** $ ./cbfstool libreboot.rom
print**
The files *grub.cfg* and *grubtest.cfg* should be present. grub.cfg is
@@ -161,8 +164,9 @@ loaded by default, with a menuentry for switching to grubtest.cfg. In
this tutorial, you will first modify and test *grubtest.cfg*. This is to
reduce the possibility of bricking your device, so DO NOT SKIP THIS!
-Extract grubtest.cfg from the ROM image:\
-**\$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg**
+Extract grubtest.cfg from the ROM image:
+
+ $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg
Modify the grubtest.cfg accordingly.
@@ -174,8 +178,9 @@ Re-insert the modified grubtest.cfg into the ROM image {#reinsert_modified_testc
------------------------------------------------------
Once your grubtest.cfg is modified and saved, delete the unmodified
-config from the ROM image:\
-**\$ ./cbfstool libreboot.rom remove -n grubtest.cfg**
+config from the ROM image:
+
+ $ ./cbfstool libreboot.rom remove -n grubtest.cfg
Next, insert the modified version:\
**\$ ./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t
@@ -190,12 +195,12 @@ Testing
**Now you have a modified ROM. Refer back to
[../install/\#flashrom](../install/#flashrom) for information on how to
-flash it.\
-\$ **cd /libreboot\_util** \# **./flash update libreboot.rom**\
+flash it.
+ $ cd /libreboot\_util** \# **./flash update libreboot.rom\
Ocassionally, coreboot changes the name of a given board. If flashrom
complains about a board mismatch, but you are sure that you chose the
-correct ROM image, then run this alternative command:\
-\# **./flash forceupdate libreboot.rom**\
+correct ROM image, then run this alternative command:
+ # ./flash forceupdate libreboot.rom
You should see **"Verifying flash\... VERIFIED."** written at the end
of the flashrom output. Once you have done that, shut down and then boot
up with your new test configuration.**
@@ -227,11 +232,13 @@ the already modified config). From /libreboot\_util/cbfstool, do:\
's:Switch to grub.cfg:Switch to grubtest.cfg:g' < grubtest.cfg >
grub.cfg**\
-Delete the grub.cfg that remained inside the ROM:\
-**\$ ./cbfstool libreboot.rom remove -n grub.cfg**
+Delete the grub.cfg that remained inside the ROM:
+
+ $ ./cbfstool libreboot.rom remove -n grub.cfg
+
+Add the modified version that you just made:
-Add the modified version that you just made:\
-**\$ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw**
+ $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw
**Now you have a modified ROM. Again, refer back to
[../install/\#flashrom](../install/#flashrom) for information on how to
diff --git a/docs/gnulinux/grub_hardening.md b/docs/gnulinux/grub_hardening.md
index cf0ef67f..81a3452b 100644
--- a/docs/gnulinux/grub_hardening.md
+++ b/docs/gnulinux/grub_hardening.md
@@ -31,6 +31,7 @@ image:
cbfstool my.rom extract -n grubtest.cfg -f my.grubtest.cfg
cbfstool my.rom remove -n grubtest.cfg
+
Helpful links:
- [GRUB manual
@@ -77,7 +78,7 @@ remember and easier to crack. Diceware passphrases are harder to crack
because of far higher entropy (there are many words available to use,
but only about 50 commonly used symbols in pass*words*).
-\-->
+-->
The GRUB password can be entered in two ways:
- plaintext
@@ -105,7 +106,7 @@ As enabling password protection as above means that you have to input it
on every single boot, we will make one menu entry work without it.
Remember that we will have GPG signing active, thus a potential attacker
will not be able to boot an arbitrary operating system. We do this by
-adding option **\--unrestricted** to a menuentry definition:
+adding option **--unrestricted** to a menuentry definition:
menuentry 'Load Operating System (incl. fully encrypted disks) [o]' --hotkey='o' --unrestricted {
...
diff --git a/docs/gnulinux/index.md b/docs/gnulinux/index.md
index 79983797..49c04dfd 100644
--- a/docs/gnulinux/index.md
+++ b/docs/gnulinux/index.md
@@ -10,6 +10,7 @@ instructions have yet to be written.**
- [How to install GNU+Linux on a libreboot
system](grub_boot_installer.html)
+
- [How to replace the default GRUB configuration file on a libreboot
system](grub_cbfs.html)
- [Installing Parabola or Arch GNU+Linux-libre with full disk
generated by cgit v1.2.3-70-g09d2 (git 2.47.1) at 2024-12-15 13:50:38 +0000