https://gist.github.com/carefree-ladka/965124eb973eb448ad117016013ec0ec
- LeetCode Patterns - Curated problem list by pattern
https://gist.github.com/carefree-ladka/965124eb973eb448ad117016013ec0ec
I've used this guide through 2024 despite archinstall and it's still more or less valid. After having
used archinstall twice and having encountered obscure issues (luksOpen taking ages, or slow
reboots in general) I switched back to a manual setup and it seems to be almost as straightforward.
Always refer to the official guide in case of doubt.
One important thing first: the environment you will encounter on the live image is very different from what you'll end up installing, some things are significantly easier there: e.g. wifi tools come
This guide is a best-effort to configure a system with just debootstrap.
It has been updated so as not to be actively incorrect as of June 2022, when I realized it was still being used, but it was first written in 2015 and I can't guarantee that it's not missing essential parts of the process.
If it breaks, you get to keep both pieces
user:live (if needed, it will probably automatically login)ip a. If you're using ethernet it should already be connected, otherwise you'll need to configure interfaces(5) and probably wpa_supplicant(8)On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software that gives developers lossless compression. This package is commonly used for compressing release tarballs, software packages, kernel images, and initramfs images. It is very widely distributed, statistically your average Linux or macOS system will have it installed for
TPM (Trusted Platform Module) is as useful for preventing real attackers as the TSA is at preventing real terrorists. The architecture is fundamentally flawed and most existing implementations are completely broken. I thought this argument was settled decades ago[1] when "trusted computing" was introduced mostly as a way to provide DRM and ownership capabilities to organizations. It has largely failed to impact the consumer market when it was introduced back in the early 2000s. However, recently there seems to be a movement by certain parties to reintroduce this failed product back to the market. Microsoft argues that in order to use Windows 11, you need TPM 2.0 compatible hardware because[2]:
The Trusted Platform Module(TPM) requirement ena
| USB Quick Start | |
| =============== | |
| XHCI controller support | |
| ----------------------- | |
| QEMU has XHCI host adapter support. The XHCI hardware design is much | |
| more virtualization-friendly when compared to EHCI and UHCI, thus XHCI | |
| emulation uses less resources (especially cpu). So if your guest |
This guide provides instructions for an Arch Linux installation featuring full-disk encryption via LVM on LUKS and an encrypted boot partition (GRUB) for UEFI systems.
Following the main installation are further instructions to harden against Evil Maid attacks via UEFI Secure Boot custom key enrollment and self-signed kernel and bootloader.
You will find most of this information pulled from the Arch Wiki and other resources linked thereof.
Note: The system was installed on an NVMe SSD, substitute /dev/nvme0nX with /dev/sdX or your device as needed.
No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.
Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.
| # On the host | |
| ============= | |
| lxc config set openvpn raw.lxc 'lxc.cgroup.devices.allow = c 10:200 rwm' | |
| lxc config device add openvpn tun unix-char path=/dev/net/tun | |
| # In the container | |
| ================== | |
| 1. mknod /dev/net/tun c 10 200 |