the beginnings of a README

This commit is contained in:
alterNERDtive 2022-07-19 11:49:36 +02:00
parent b6fa0cabed
commit 9495212a2c
Signed by: alterNERDtive
GPG key ID: 547787A4FE6533F1
2 changed files with 48 additions and 0 deletions

View file

@ -1,6 +1,45 @@
# GPGTool
Zsh script to manage GPG keys without storing the master key.
GPG lets you have sub keys for encryption and for signing without having access
to the secret part of the master key. That way you can use your GPG key without
fear of having your secure identity compromised should you ever “lose” your
keys.
An attacker will be able to use the currently valid sub keys until you revoke
them. They will _never_ be able to create new sub keys for your master key.
So in case of compromise of your GPG key(s), whip out your securely stored
master key, invalidate your current sub keys, make sure to propagate that e.g.
via key server and generate new sub keys.
## Installation
Download / clone this repo and put it somewhere. Either run `gpgtools` from
there directly or put it in your `PATH`.
If you want to package this for your flavour for \*nix, go ahead. Its GPL.
## Usage
FIXXME
## (Optional) Configuration File
FIXXME
See [`gpgtool.example.conf`](gpgtool.example.conf).
## F.A.Q.
**Q:** I want this as a bash script!
**A:** Thats not a question.
**Q:** Can I have this as a bash script?
**A:** No.
[![GitHub Sponsors](https://img.shields.io/github/sponsors/alterNERDtive?style=for-the-badge)](https://github.com/sponsors/alterNERDtive)
[![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/S6S1DLYBS)

9
gpgtool.example.conf Normal file
View file

@ -0,0 +1,9 @@
# One of GPGTOOLDIR or GPGTOOLDEV is required. If GPGTOOLDEV is given GPGTOOLDIR
# will be treated as relative to the mount point of GPGTOOLDEV.
# Path to the key directory.
# Can be set with `-p` `--directory`.
GPGTOOLKEYPATH=/path/to/key/directory/
# Path to the device that holds the key directory, e.g. a USB flash drive.
# Can be set with `-d` `--device`
GPGTOOLKEYDEV=/path/to/device