瀏覽代碼

Also publish backup public key to avoid sync error messages

This shouldn't introduce any security issues
Bob Mottram 8 年之前
父節點
當前提交
a152697dc3
共有 1 個文件被更改,包括 4 次插入0 次删除
  1. 4
    0
      src/freedombone-controlpanel-user

+ 4
- 0
src/freedombone-controlpanel-user 查看文件

@@ -35,6 +35,7 @@ export TEXTDOMAINDIR="/usr/share/locale"
35 35
 
36 36
 MY_EMAIL_ADDRESS=$USER@$HOSTNAME
37 37
 GPG_ID=$(gpg --fingerprint $MY_EMAIL_ADDRESS | grep -i "pub" | head -n 1 | awk -F '/' '{print $2}' | awk -F ' ' '{print $1}')
38
+GPG_BACKUP_ID=$(gpg --fingerprint "$MY_EMAIL_ADDRESS (backup key)" | grep -i "pub" | head -n 1 | awk -F '/' '{print $2}' | awk -F ' ' '{print $1}')
38 39
 
39 40
 UTILS_FILES=/usr/share/${PROJECT_NAME}/utils/${PROJECT_NAME}-utils-*
40 41
 for f in $UTILS_FILES
@@ -404,6 +405,9 @@ function show_gpg_key {
404 405
 
405 406
 function publish_gpg_key {
406 407
     gpg --send-key $GPG_ID
408
+    if [ $GPG_BACKUP_ID ]; then
409
+        gpg --send-key $GPG_BACKUP_ID
410
+    fi
407 411
     dialog --title $"Publish your PGP/GPG key" \
408 412
            --msgbox $"Your key has now been published" 6 40
409 413
 }