This is a guide on how to email securely.
There are many guides on how to install and use PGP to encrypt email. This is not one of them. This is a guide on secure communication using email with PGP encryption. If you are not familiar with PGP, please read another guide first. If you are comfortable using PGP to encrypt and decrypt emails, this guide will raise your security to the next level.
| # Copied from https://github.com/aseprite/aseprite/blob/master/INSTALL.md#skia-on-linux | |
| sudo yum install -y gcc-c++ cmake ninja-build libX11-devel libXcursor-devel mesa-libGL-devel fontconfig-devel | |
| mkdir $HOME/deps | |
| cd $HOME/deps | |
| git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git | |
| git clone -b aseprite-m71 https://github.com/aseprite/skia.git | |
| export PATH="${PWD}/depot_tools:${PATH}" | |
| cd skia |
On my yourney though hundreds of videos, tutorials and manuals (Bardwell, UAV Tech, JohnnyFPV, Mr. Steele, Le Drib, RotorRiot (sorry, for the missed ones) and wrote down their suggestions). This is the result of my notes. It should provide the least necessary but most compressed information to start tuning and setting your Quadcopter.
In my case I use the widely spread Taranis X7 remote control.
I am a freestyle pilot, so keep in mind, that these settings are in this scope (more smooth, softer flight behaviour).
On my yourney though hundreds of videos, tutorials and manuals (Bardwell, UAV Tech, JohnnyFPV, Mr. Steele, Le Drib, RotorRiot (sorry, for the missed ones) and wrote down their suggestions). This is the result of my notes. It should provide the least necessary but most compressed information to start tuning and setting your Quadcopter.
In my case I use the widely spread Taranis X7 remote control.
I am a freestyle pilot, so keep in mind, that these settings are in this scope (more smooth, softer flight behaviour).
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.
| # Install ARCH Linux with encrypted file-system and UEFI | |
| # The official installation guide (https://wiki.archlinux.org/index.php/Installation_Guide) contains a more verbose description. | |
| # Download the archiso image from https://www.archlinux.org/ | |
| # Copy to a usb-drive | |
| dd if=archlinux.img of=/dev/sdX bs=16M && sync # on linux | |
| # Boot from the usb. If the usb fails to boot, make sure that secure boot is disabled in the BIOS configuration. | |
| # Set swedish keymap |
References:
http://www.muktware.io/arch-linux-guide-the-always-up-to-date-arch-linux-tutorial/ (Link is broken)There are 2 choices:
I tried to install in UEFI mode, but my laptop (Acer E5-475-336H) had problems with it, and didn't boot after installation.
| // ==UserScript== | |
| // @name Auto Check-In to Southwest Flights | |
| // @namespace http://www.ryanizzo.com/southwest-auto-check-in/ | |
| // @version 1.8 | |
| // @author Nicholas Buroojy (http://userscripts.org/users/83813) | |
| // @contributor Ryan Izzo (http://www.ryanizzo.com) | |
| // @contributor JR Hehnly (http://www.okstorms.com @stormchasing) | |
| // @contributor Trevor McClellan (github.com/trevormcclellan) | |
| // @description Automatically check in to Southwest Airline flights at the appropriate time. | |
| // @include https://www.southwest.com/air/check-in/index.html* |
| [global] | |
| trackers_file = /path/to/zeronet_trackers.txt |
Its easy to setup a LAN between two Ubuntu machines connected over ethernet. If one of those machines, which we will call the server, is also connected to the internet via another device (like a wireless card) it will automagically share its internet connection as well. Begin by connecting the client and server machines via ethernet.
On the server machine, click the network icon on the top right and select "Edit Connections > Wired connection 1 > Edit > IPv4 Settings" and change "Method" to "Shared to other computers". Then open the network icon menu again and click "Wired connection 1" to ensure that the connection has been established. Running ifconfig in the terminal should show that the wired interface has an ip address.
On the client machine, click the network icon on the top right and select "Wired connection 1". All done. Run ifconfig on this machine as well to see the ip address you've been assigned.