Log these commands too, no reason not to.
This commit is contained in:
parent
8797b2049b
commit
1a0cdd21e8
1 changed files with 2 additions and 0 deletions
|
@ -13,7 +13,9 @@ temp=~/.gnupg
|
||||||
[[ $overgpg == n || $ovrgpg == N ]] && read -p "GPG home [$temp]: " gpghome
|
[[ $overgpg == n || $ovrgpg == N ]] && read -p "GPG home [$temp]: " gpghome
|
||||||
gpghome=${gpghome:-~/.gnupg}
|
gpghome=${gpghome:-~/.gnupg}
|
||||||
echo "[INFO] Ensuring '$gpghome' exists with the correct permissions"
|
echo "[INFO] Ensuring '$gpghome' exists with the correct permissions"
|
||||||
|
echo "$ mkdir -p $gpghome"
|
||||||
mkdir -p "$gpghome"
|
mkdir -p "$gpghome"
|
||||||
|
echo "$ chmod 700 $gpghome"
|
||||||
chmod 700 "$gpghome"
|
chmod 700 "$gpghome"
|
||||||
echo '[INFO] Now creating a gpg key using the real name and email provided'
|
echo '[INFO] Now creating a gpg key using the real name and email provided'
|
||||||
echo "$ GPGHOME=$gpghome gpg --default-new-key-algo rsa4096 --quick-gen-key --batch --passphrase '' \"$rname <$email>\""
|
echo "$ GPGHOME=$gpghome gpg --default-new-key-algo rsa4096 --quick-gen-key --batch --passphrase '' \"$rname <$email>\""
|
||||||
|
|
Loading…
Reference in a new issue