This gist aims to facilitate the switching from bash to zsh as our defaut shell.
We will be using oh-my-zsh with the powerful theme: Powerlevel9k. You will find all the links below.
This process applies mainly for Arch Linux, but can be setup for any other distro (in theory :)).
I'm also using Gnome Terminal and pacaur as package manager.
| # This installation guide will create basic working arch linux installation with encryption. | |
| # Encryption is implemented with dm-crypt + LUKS on a single disk. | |
| # Following articles/posts/gists were used as reference | |
| # https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/ | |
| # https://wiki.archlinux.org/index.php/Installation_guide | |
| # https://wiki.archlinux.org/index.php/Dm-crypt/System_configuration | |
| # https://wiki.archlinux.org/index.php/Dm-crypt/Device_encryption | |
| # https://blog.tinned-software.net/automount-a-luks-encrypted-volume-on-system-start/ | |
| # https://gist.github.com/mattiaslundberg/8620837 |
References:
- https://gist.github.com/mattiaslundberg/8620837
- https://wiki.archlinux.org/index.php/Installation_guide
http://www.muktware.io/arch-linux-guide-the-always-up-to-date-arch-linux-tutorial/(Link is broken)
There are 2 choices:
- UEFI/GPT mode: UEFI boot mode / GPT partition table
- BIOS/MBR mode: Legacy boot mode / MBR partition table
I tried to install in UEFI mode, but my laptop (Acer E5-475-336H) had problems with it, and didn't boot after installation.
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.
| #!/bin/bash | |
| #Paths are for Centos 7.x | |
| # Install optional packages | |
| /usr/bin/yum install -y epel-release | |
| /usr/bin/yum install -y bash-completion htop yum-utils dkms open-vm-tools | |
| #stop logging services | |
| /sbin/service rsyslog stop | |
| /sbin/service auditd stop |
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
| # Version 1.2 :: This script reads offline event logs, oldest to newest, bottom to top. | |
| # See http://www.trimideas.com/2015/04/auditing-changed-deleted-files.html for instructions. | |
| $LogPath = "C:\Event_Logs\" | |
| $ReportPath = "C:\Audit\File-Audit-Reports\" | |
| $Formatted_Date = (Get-Date -UFormat %A-%B-%d-at-%I-%M-%S%p) | |
| $ZipName = "Security-Events-for-" + (Get-Date -UFormat %A-%B-%d) + ".zip" | |
| $Report_in_CSV = $ReportPath + "Audit of changed files on " + $Formatted_Date + ".csv" | |
| $Truncated_Log_Path = $LogPath + "Archive-Security_on_" + $Formatted_Date + ".evtx" | |
| $Today_Midnight = (Get-Date -Hour 0 -Minute 0 -Second 0) |
Software required:
After installation and putting the youtube-dl in PATH
youtube-dl \