From 47a4741a3cfb256ac0348c97d14ad79a0ff2618d Mon Sep 17 00:00:00 2001 From: Lars Gustäbel Date: Sun, 2 Feb 2014 16:29:14 +1000 Subject: Prevent makepkg creating armored signatures If the user has "armor" in thier gpg.conf, makepkg will create an ascii-armored signature. Use --no-armor in the gpg call to avoid. FS#38503. Signed-off-by: Allan McRae --- scripts/makepkg.sh.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'scripts') diff --git a/scripts/makepkg.sh.in b/scripts/makepkg.sh.in index 7d8a676b..e3d9a936 100644 --- a/scripts/makepkg.sh.in +++ b/scripts/makepkg.sh.in @@ -1968,7 +1968,7 @@ create_signature() { SIGNWITHKEY="-u ${GPGKEY}" fi # The signature will be generated directly in ascii-friendly format - gpg --detach-sign --use-agent ${SIGNWITHKEY} "$filename" &>/dev/null || ret=$? + gpg --detach-sign --use-agent ${SIGNWITHKEY} --no-armor "$filename" &>/dev/null || ret=$? if (( ! ret )); then -- cgit v1.2.3-70-g09d2