[pkg-gnupg-maint] [Pkg-ltsp-devel] Bug#831409: ltsp-client lacks gnupg / gnupg2 for apt-key to work

[Daniel Kahn Gillmor]

[ adding pkg-gnupg-maint to the cc list ]

On Mon 2016-07-18 17:19:13 +0200, Holger Levsen <holger at layer-acht.org> wrote:
> On Mon, Jul 18, 2016 at 08:02:40AM -0700, Vagrant Cascadian wrote:
>> At any rate, Wolfgang Schweer confirmed that adding it to the
>> debootstrap includes worked around the issue, although then we'd have
>> the problem of deciding on gnupg vs. gnupg2, and at some point gnupg
>> will disappear.
>
> I believe we should stop using gnupg and switch to gnupg2 in sid, cc:
> Daniel for input on this.

the gnupg2 source package in experimental provides the "gnupg" binary
package, while the "gnupg" binary package in experimental provides a
"gnupg1" binary package.  confusing, right? :P  

I will probably rename the gnupg source package to "gnupg1" to make the
names slightly less confusing before it lands in experimental.

But the point is that the "gnupg" binary package will continue to exist,
so if you have to pick one you should pick it :)

But i think that the better solution is to avoid using apt-key in the
way you're talking about using it.  It's much better to place the
OpenPGP binary format key that you care about directly into
/etc/apt/trusted.gpg.d/$FOO

If you've got it in ascii-armored format and aren't sure how to decode
it, you should be able to do that with a short awk | base64 -d pipeline:

  awk '/^$/{ x = 1; } /^[^=-]/{ if (x) { print $0; } ; }' | base64 -d 

hth,

   --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20160718/b334524e/attachment.sig>