[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-users
Subject:    =?utf-8?Q?Re:_[cross_post]_Why_does_verification_of_a_detached_signature_result_in_a_=E2=80=9CMessag
From:       cqcallaw via Gnupg-users <gnupg-users () gnupg ! org>
Date:       2020-11-28 20:54:10
Message-ID: WT26gmZu537Xzi-Nn6Ti_hSys9g34Tc2U44fXOrUK8s5aJ7OCNLXiwfXC34jJHUe0eF6-6vA0GE19hjurNnS4q2TkF7BRJ6XX6oXhg1MkI0= () brainvitamins ! net
[Download RAW message or body]

------- Original Message -------
On Saturday, November 28, 2020 7:38 AM, Ingo Klöcker <kloecker@kde.org> wrote:

> On Freitag, 27. November 2020 23:52:27 CET cqcallaw via Gnupg-users wrote:
> Could be a problem with text mode vs. non-text mode. By default, gpg uses non-
> text mode when signing something. Try adding --textmode to gpg's command line.
>
> > let msg = await openpgp.cleartext.fromText(msg_data);
>
> This is just a wild guess, but fromText() could imply text mode in OpenPGP.js.

Excellent, adding --textmode to gpg's command line resolved the issue.

Thanks!
-Caleb

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
[prev in list] [next in list] [prev in thread] [next in thread]