gnupg 2.1 vs rpmsign

Mon Nov 24 12:40:12 CET 2014

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 11/24/2014 11:04 AM, Dimitri John Ledkov wrote:
> It appears that rpmsign does not co-operate well enough with
> gnupg.
> 

...

> What should rpmsign be doing instead? (cause it looks like 
> --passphrase-fd option is no longer supported by gpg 2.1)

Look into --pinentry-mode loopback[0]

> 
> E.g. should it use gpg-preset-passphrase --passphrase STRING and
> then invoke gpg command?
> 

That would also work

References
[0] http://lists.gnupg.org/pipermail/gnupg-devel/2013-February/027345.html


- -- 
- ----------------------------
Kristian Fiskerstrand
Blog: http://blog.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Public OpenPGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
- ----------------------------
"I never worry about action, but only inaction."
(Winston Churchill)
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJUcxkbAAoJEPw7F94F4Tag0l8P/jZfvFM5MJsexrA+FfanIU6h
RVLz87yI3RadlVAz+CJAeFXsA7ZbHOMDFwaCPFIp2xDiKw2oJ8OHjaRm1QjalH/a
z4A5d12Ma1P7HGRsXIMjQjZAp/twnUij+xoRXJf4pK5P4UOQfRqKQfgGO2o+XanR
8VfRRULqKZOWlaKei1yMH2xD7sOzUX6oqnvN7107jwzm4CVqOd1jomuvS3qcK/zc
LcKqPlioN3fjNLJCX0jG5K7OuDeiyachVZeivZqc27v5cPMCJbvkgHfGEniUqZmc
/B7A31qMLcTSxqC4e82I5o9Mi2L/mz7W0rms2KpAAX8D0Sy12rZEsflM1unPE+tp
O0+RRiInIrEMAtNpfaBKwZ8xzhaGqJT073CNb6eHUopSsMBzjfiMCg5CLIvDpuy+
uU1WHQ7uqoA+9/zI7YRCaumIOJ3Tnm/nOtL4Rgfas/EBFmQ8oTdfKLbv5hNcizAX
tPgTTml92amhQUQFlSecCPY9ebz8WZU2+5n/HEETFrNpIX7gZzNvdj76FrXmg6hr
tToE/O56392kpGWDJYpUXjhT8EmuQ1tjHU9cOGADQrlAqEY1apo5k8wYFVI1pzOP
4OIAB2l2cV/QfVARqVqsv4d8AONzusqPM7QpP/JIjz0Zot0DliN63CIL+lHnR/JL
1LE/HwwXF2npN+wV/AfG
=CoIo
-----END PGP SIGNATURE-----