Also publish backup public key to avoid sync error messages
This shouldn't introduce any security issues
This commit is contained in:
parent
574f1de273
commit
a152697dc3
|
@ -35,6 +35,7 @@ export TEXTDOMAINDIR="/usr/share/locale"
|
||||||
|
|
||||||
MY_EMAIL_ADDRESS=$USER@$HOSTNAME
|
MY_EMAIL_ADDRESS=$USER@$HOSTNAME
|
||||||
GPG_ID=$(gpg --fingerprint $MY_EMAIL_ADDRESS | grep -i "pub" | head -n 1 | awk -F '/' '{print $2}' | awk -F ' ' '{print $1}')
|
GPG_ID=$(gpg --fingerprint $MY_EMAIL_ADDRESS | grep -i "pub" | head -n 1 | awk -F '/' '{print $2}' | awk -F ' ' '{print $1}')
|
||||||
|
GPG_BACKUP_ID=$(gpg --fingerprint "$MY_EMAIL_ADDRESS (backup key)" | grep -i "pub" | head -n 1 | awk -F '/' '{print $2}' | awk -F ' ' '{print $1}')
|
||||||
|
|
||||||
UTILS_FILES=/usr/share/${PROJECT_NAME}/utils/${PROJECT_NAME}-utils-*
|
UTILS_FILES=/usr/share/${PROJECT_NAME}/utils/${PROJECT_NAME}-utils-*
|
||||||
for f in $UTILS_FILES
|
for f in $UTILS_FILES
|
||||||
|
@ -404,6 +405,9 @@ function show_gpg_key {
|
||||||
|
|
||||||
function publish_gpg_key {
|
function publish_gpg_key {
|
||||||
gpg --send-key $GPG_ID
|
gpg --send-key $GPG_ID
|
||||||
|
if [ $GPG_BACKUP_ID ]; then
|
||||||
|
gpg --send-key $GPG_BACKUP_ID
|
||||||
|
fi
|
||||||
dialog --title $"Publish your PGP/GPG key" \
|
dialog --title $"Publish your PGP/GPG key" \
|
||||||
--msgbox $"Your key has now been published" 6 40
|
--msgbox $"Your key has now been published" 6 40
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue