1. Forum
  2. FidoNet
  3. PUBLIC KEYS

  • Re: gpg: invalid armor header: Â \r\n

    From Wilfred van Velzen@2:280/464 to August Abolins on Sun Jan 26 13:12:35 2020
    Hi August,

    On 2020-01-26 04:24:19, you wrote to me:

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    Let's see how the signed clear-text behaves.

    This signature was ok...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From August Abolins@2:221/360 to Wilfred van Velzen on Sun Jan 26 18:49:36 2020
    On 1/26/2020 7:12 AM, between "Wilfred van Velzen : August Abolins":

    AA> Let's see how the signed clear-text behaves.

    This signature was ok...

    Thanks for confirming. That one went out with UTF-8 encoding, but my
    own copy (viewing locally) did not verify! :(

    gpg command line and output:
    C:\Program Files\gnupg\bin\gpg.exe
    gpg: Signature made 01/25/20 21:24:15 Eastern Standard Time
    gpg: using RSA key D0EB2A295204F3167EB2503CEF0E89655789589B
    gpg: BAD signature from "August Abolins <august@kolico.ca>" [ultimate]


    So, it seems that clear-text signing is only gonna work if I avoid UTF-8 charset and stick with ISO 8859-1.

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)