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

Vagrant Cascadian vagrant at debian.org
Sat Sep 3 03:24:19 UTC 2016


Control: tags 831409 pending

On 2016-07-18, Daniel Kahn Gillmor wrote:
> 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:
> 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 

Thanks!

Implemented the above in a couple commits upstream:

  https://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2746
  https://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2747


Hope to upload the fix soon.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/attachments/20160902/64380a1c/attachment.sig>


More information about the Pkg-ltsp-devel mailing list