Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.
cp ~/.gnupg/pubring.gpg /path/to/backups/
cp ~/.gnupg/secring.gpg /path/to/backups/
cp ~/.gnupg/trustdb.gpg /path/to/backups/
It sometimes happen you need change code on a machine from which you cannot push to the repo.
You’re ready to copy/paste what diff outputs to your local working copy.
You think there must be a better way to proceed and you’re right. It’s a simple 2 steps process:
1. Generate the patch:
git diff > some-changes.patch
| # disable auto rotation | |
| adb shell content insert --uri content://settings/system --bind name:s:accelerometer_rotation --bind value:i:0 | |
| # force landscape | |
| adb shell content insert --uri content://settings/system --bind name:s:user_rotation --bind value:i:1 | |
| # back to portrait | |
| adb shell content insert --uri content://settings/system --bind name:s:user_rotation --bind value:i:0 | |
| # upside down |
For verifying the integrity (but not authenticity of data, i.e., who authored it or the origin of the file) of a file, it is necessary to run a checksum function on the file which will output a value and compare it to a previously stored checksum value; if both values match, we can be relatively confident that the file hasn't been tampered with or altered.
You might be asked to verify a file's sha1sum or sha2sum–-all this means is calculating and verifying the cryptographic sha1 or sha2 hash value or digest included in the file.
Organic:
In terminal run:
| #!/bin/bash | |
| iatest=$(expr index "$-" i) | |
| ####################################################### | |
| # SOURCED ALIAS'S AND SCRIPTS BY zachbrowne.me | |
| ####################################################### | |
| # Source global definitions | |
| if [ -f /etc/bashrc ]; then | |
| . /etc/bashrc |
Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.
Gotten from the RedHat GPG migration manual
## Export all public keys
gpg -a --export >mypubkeys.asc
| # This sample template explores how we can turn the Telegram blog post on the left into an Instant View page as shown on the right — in several simple steps. If you're unsure what some of the elements used here do, check out the full documentation here: https://instantview.telegram.org/docs | |
| # Place the version at the beginning of template. We recommend always using the latest available version of Instant View. | |
| ~version: "2.0" | |
| ### STEP 1: Define which pages get Instant View and which don't | |
| # That's easy because we only need IV pages for posts on the Telegram blog. | |
| # This *condition* does the trick. | |
| # ?path: /blog/.+ |
| # To remove only some text on a content | |
| @remove: //p[self::p/strong[contains(text(), "Articles liés")]] | |
| @remove: //iframe[contains(@src,"https://urlsomething")] | |
| # To deal with fucking error of <img> is not supported in blabla | |
| @before_el(./..): //a/img | |
| @before_el(./..): //p/img |