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

On 07/01/2020 8:10 a.m., mark lewis : August Abolins wrote:

encrypted and/or signed messsges are allowed in this echo...
AFAIK, this is the only echo that allows such

I recently updated my Win7 pc to TB 68 + the corresponding
Enigmail/GPG plugin.

But signed clear-text email seems to be rolling out with:

gpg command line and output:
C:\Program Files\gnupg\bin\gpg.exe
gpg: invalid armor header: Â \r\n
gpg: invalid armor header: Â \r\n


Signed clear-text messages from other people in this echo look good
and process properly.

So, I am testing one originating from this new TB68/Enigmail combo to
see if the "invalid armor header" is a problem here.

I'd hate to roll back TB. But maybe all I have to do is rollback the
Enigmail plugin version?


- --
Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4scOIACgkQ7w6JZVeJ WJugNQf/TcvM1zQJi8hN42CQDCtsTbX0hu2B/Smg3k/zy6aCB5FabIRGxgQCt3C0 yROmIvUpLLwQQ8MMwzYqQfvb25ifmt1NwCNHl2sPSQVeIUQPaU/6PNeikgSNhmXH w7SxK7upP17sAjIY3sG+lOto2S6HgDtt8MVyZrbr4BAUK6EfG475oTsKgo3jezTc ALa2W3tVByYS6TlnvuyqEFJkbShw6ddl+lIclYsK3A8B0y4S+rOLlklUyloUbVY1 u4BBpQAyWXzwLb9Mfm7W/X0pcCzlxCEtn4RXblMg9o7UnVNviYupc31HbLCAo/FO 61EYIA3M6lOe/QCfx6jk62qF+xFNLg==
=iByN
-----END PGP SIGNATURE-----

--- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

Hi August,

On 2020-01-25 18:46:39, you wrote to mark lewis:

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

On 07/01/2020 8:10 a.m., mark lewis : August Abolins wrote:

encrypted and/or signed messsges are allowed in this echo...
AFAIK, this is the only echo that allows such

I recently updated my Win7 pc to TB 68 + the corresponding
Enigmail/GPG plugin.

But signed clear-text email seems to be rolling out with:

gpg command line and output:
C:\Program Files\gnupg\bin\gpg.exe
gpg: invalid armor header: Â \r\n
gpg: invalid armor header: Â \r\n

Signed clear-text messages from other people in this echo look good
and process properly.

So, I am testing one originating from this new TB68/Enigmail combo to
see if the "invalid armor header" is a problem here.

I'd hate to roll back TB. But maybe all I have to do is rollback the Enigmail plugin version?

- --
Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc -----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4scOIACgkQ7w6JZVeJ WJugNQf/TcvM1zQJi8hN42CQDCtsTbX0hu2B/Smg3k/zy6aCB5FabIRGxgQCt3C0 yROmIvUpLLwQQ8MMwzYqQfvb25ifmt1NwCNHl2sPSQVeIUQPaU/6PNeikgSNhmXH w7SxK7upP17sAjIY3sG+lOto2S6HgDtt8MVyZrbr4BAUK6EfG475oTsKgo3jezTc ALa2W3tVByYS6TlnvuyqEFJkbShw6ddl+lIclYsK3A8B0y4S+rOLlklUyloUbVY1 u4BBpQAyWXzwLb9Mfm7W/X0pcCzlxCEtn4RXblMg9o7UnVNviYupc31HbLCAo/FO 61EYIA3M6lOe/QCfx6jk62qF+xFNLg==
=iByN
-----END PGP SIGNATURE-----

I'm getting:

gpg: Signature made za 25 jan 2020 17:46:26 CET using RSA key ID 5789589B
gpg: BAD signature from "August Abolins <august@kolico.ca>" [unknown]

On this one...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

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

On 1/25/2020 3:42 PM, between "Wilfred van Velzen : August Abolins":

I recently updated my Win7 pc to TB 68 + the corresponding
Enigmail/GPG plugin.

But signed clear-text email seems to be rolling out with:

gpg command line and output:
C:\Program Files\gnupg\bin\gpg.exe
gpg: invalid armor header: Â \r\n
gpg: invalid armor header: Â \r\n

I'm getting:

gpg: Signature made za 25 jan 2020 17:46:26 CET using RSA key ID

5789589B

gpg: BAD signature from "August Abolins <august@kolico.ca>" [unknown]

On this one...

THANK YOU.

Something is wrong with TB 68 + Enigmail. I am guessing it might have
to do with using UTF-8 for message encoding with that system.

The invalid "Â" char in the PGP block is suspect of that cause.

- From my quick initial research, there is supposed to be the equivalent
of a &nbsp; where the "Â" shows up in the block.

Meanwhile, this time, THIS message is originating from the TB 20.0.0.4.
I am using UTF-8 message encoding, like I have configured for these
nntp message areas here.

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


-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4s+E8ACgkQ7w6JZVeJ WJts8wgApfinpTTIUpnag4dTVFFXRo21CW847SRm/xuNCWbvBRaxLTxDhf3gV5wo RsiRMCTx1hoFYaS1ZpWg0ZixcbasHvAfz5OBX3wN8is9NW94lxaQOhUYxoi2vZ9C dvN10bvTWoorWfCYt7kkbdFfVkJynEb8vO2HfCBcy6XxRz+a4BNgqs3qNPs36Juv YN/w8qlWYFPEOr0HuLCulpHBqDvPT1r/aS7yK7MIE6B2v36GPYT4DxKQGNyQP3HE GziAzVlzJVumt5HpLT9wjgPdn6VvOTPM4EPkxLcN0z1fsZHY/h5RhkcgrAFnRUhp qfD2gJI4TomJY03c7aTc8/3wMiFUug==
=VfXg
-----END PGP SIGNATURE-----

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

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)

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)