| /* Dubyas list of annoying stuff he hides in discord using Quick CSS */ | |
| /* Want to have this be synced up with your Discord so you don't need to re-copy and paste this for new additions? | |
| * Feel free to just import this gist directly by adding the following line: | |
| * @import url("https://gist.githubusercontent.com/DubyaDude/1ee0e8c218a22883721635dfae3e022c/raw/DubyasCleanupOfDiscord.css"); | |
| */ | |
| /* Disable profile edit page upsell */ | |
| div[id="profile-customization-tab"] > div[class^="container_"] | |
| { |
This simple Gist will explain how to settup your GPG key to work for SSH authentication (with Git) and Git commit signing on Windows 10. This may seem straightforward on Linux, but there are certain tweaks needed on Windows.
No Cygwin, no MinGW, no Git Bash or any other Linux emulated environment. This works in pure Windows 10.
You're running a KVM-based virtualization. You want to do PCI/PCIe passthrough of some device. You don't want it to attach to the host OS at all.
Your device looks like that:
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 6 port Desktop SATA AHCI Controller [103c:330d]
Kernel driver in use: ahci
Kernel modules: ahci
Here we create the master key. We want only Certify capability: we use the master key only to create the subkeys, Sign - Encrypt - Authenticate capabilities will be assigned to the subkeys.
Run the following command to start the master key generation process. Select the set your own capabilities creation process (type 8)
▶ gpg --full-generate-key --expert
gpg (GnuPG) 2.2.9; Copyright (C) 2018 Free Software Foundation, Inc.