Subject: bug#3829: 23.0.96; Cannot read gpg file

From: Lars Ingebrigtsen <[email-masked]>
Date: Tue, 04 Aug 2020 21:43:46 +0200

Lars Ingebrigtsen <[email-masked]> writes:

> On the other hand, we could just let gpg try to decrypt the data and if
> we get
>
> gpg -d /tmp/trusted.gpg 
> gpg: decrypt_message failed: Unexpected error
>
> then we can just take that as a hint that it's not encrypted data and
> then insert the bytes instead.

I've now done this on the trunk.  I think it's a better, less annoying
behaviour than before...  probably.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no