1. Forum
  2. FidoNet
  3. PUBLIC KEYS

  • Re: using ISO 8859-1

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

    On 2020-01-26 04:29:37, you wrote to All:

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

    This time, I am avoiding UTF-8.

    I have a funny feeling this is the crux of the matter.

    Also verified 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:42:51 2020
    On 1/26/2020 7:13 AM, between "Wilfred van Velzen : August Abolins":

    AA> This time, I am avoiding UTF-8.
    AA> I have a funny feeling this is the crux of the matter.

    Also verified ok...

    Thank you. Looks like clear-signed messages MUST be posted in plain
    ASCII only. Or, at least that is the situation with TB/Enigmail.

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From August Abolins@2:221/360 to August Abolins on Mon Jan 27 17:13:12 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    On 25/01/2020 9:29 p.m., August Abolins : All wrote:
    This time, I am avoiding UTF-8.

    I have a funny feeling this is the crux of the matter.


    YEP. That one processed without errors. .: must avoid utf-8 encoding
    when using signed clear-text. TB must be munging/substituting the
    space char with the utf-8 equivalent AFTER generating the block.





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

    iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4u/f4ACgkQ7w6JZVeJ WJsXQAf8CB5bx9oQ0ctv5U+/An9F1guUCFe0A38FY9w/CmKS9QS4dSeBFj2eZIJy AHKTyh2WzhFX1NGCYkfiaD959cBbBsDWcb3qPiKgIlPt2Zb1KUhHJ9mV7PRgpFCN mwOj8gXksk9z6HLi4vpoyvL4PSPVl2lcThx+aaaqskN2SVVslT+qNmNFxhKz2T84 /1gJRMbgLsqFSZdjqyg6/8N8x8yzXHUIBV2Mp78deq4URb63QHPUOCrgXpIq1uvg YnCpcVTGsMjuoRjC8wCsRUf6/ilg5KufuKmnyfU6qL67Tu5TirX8FInOQ9RZWuDm ZkwRw88TTTqMPzMrMzBrHMwXxnnVAg==
    =y+cx
    -----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)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Mon Jan 27 16:37:49 2020
    Hi August,

    On 2020-01-27 17:13:12, you wrote to you:

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

    On 25/01/2020 9:29 p.m., August Abolins : All wrote:
    This time, I am avoiding UTF-8.

    I have a funny feeling this is the crux of the matter.


    YEP. That one processed without errors. .: must avoid utf-8 encoding
    when using signed clear-text. TB must be munging/substituting the
    space char with the utf-8 equivalent AFTER generating the block.

    gpg: Signature made Mon Jan 27 16:13:02 2020 CET using RSA key ID 5789589B
    gpg: Good signature from "August Abolins <august@kolico.ca>" [unknown]
    gpg: aka "August Abolins <august@R_E_M_O_V_Ekolico.ca>" [unknown]


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/360.8110 to August Abolins on Mon Jan 27 21:21:30 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256


    On 26.01.2020 18:42, August Abolins wrote:

    Thank you. Looks like clear-signed messages MUST be posted in
    plain ASCII only. Or, at least that is the situation with
    TB/Enigmail.

    Also the combination "JamNNTPd + UTF-8" may be the reason...

    'Tommi




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

    iQEzBAEBCAAdFiEEQTJnraOsQBoYwCPS0ikymSpvgioFAl4vODkACgkQ0ikymSpv gioEFwf8D/WpKs+C604jTvLA5qggfkpchP10mg5Zx3W1WRrrF+5B8DUYQoC+5wRp iH27bFMC4bXTOCG3hCRUXuV9vE1WWH/H/11iRPo/7TKm7B7qO2f/379D7wiQytKh 4XGS+pwDEHwaRYOk22jHjQcDHywf0u1s35xpDfTvB7H9AhmhHPnUgZZFIbqvZH/d fBN1UOP/j8gfTSrHUqyya2BpUaqu+V/wnT0jFIYMuFheVfuDNLCOfO8D6kclkScg N+uYyrFx/qjIDDP2YZDUW9gKJIH5KLXF4ebpqlWtmMfme9qNwRbNICref5uHpQIU M+RoC31eCnttlunTVDhEGM3NxeEW2g==
    =k66Z
    -----END PGP SIGNATURE-----
    ---
    * Origin: nntp point (2:221/360.8110)
  • From August Abolins@2:221/360 to Tommi Koivula on Mon Jan 27 23:42:07 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    On 27/01/2020 2:21 p.m., Tommi Koivula : August Abolins wrote:


    Thank you. Looks like clear-signed messages MUST be posted in
    plain ASCII only. Or, at least that is the situation with
    TB/Enigmail.

    Also the combination "JamNNTPd + UTF-8" may be the reason...
    Origin: nntp point (2:221/360.8110)


    Yours with utf-8 decoded fine:

    Enigmail Security Info
    Part of the message signed
    Good signature from Tommi Koivula <tommi@rbb.fidonet.fi>

    (I still have to see how TB24 at my other pc handles it.)

    But you're adding new variables with the way you are processing the
    point source. At least you have a clean option.

    OK, this one going back to you with utf-8 from my TB/Enigmail combo.

    It will probably fail.
    -----BEGIN PGP SIGNATURE-----

    iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4vWSgACgkQ7w6JZVeJ WJujywgA0eT3S7TlMPbmYBoUoPcNasPeG4vm8vgTzmRh6ga8DzEdEH80yj83uELw Vo4wC9UMyFw++V+ViEeo3bhq3NvEtVH1eCA0fPO4OZ5ZtGg8N8mRXQLbSGMtO82n NACs3ZUt7Yg6W2VE7JXGNOe9y1EFgSqsLf8Jt9mA8uozXez05WX8GwY/YgbBJEqB eUaLt8qY+UmP70eg7H0cPWtkxK3deQHVU56pEVsXGK9wmDhbvP/nL8KWOMh9y1ji BWbOEHm8esEVr6mR/7qK9U/ij+pZ5773SmFD0zQiNsNfKBvrqlpf0Cu2khh4Ssp9 qkyUkXhB+5ykkaIxh7belr8x5KgEGg==
    =Mgin
    -----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)
  • From August Abolins@2:221/360 to Tommi Koivula on Tue Jan 28 01:56:31 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    On 1/27/2020 2:21 PM, between "Tommi Koivula : August Abolins":

    Also the combination "JamNNTPd + UTF-8" may be the reason...
    ---
    * Origin: nntp point (2:221/360.8110)

    That one of yours arrived as Content-Type: text/plain;
    charset=ISO-8859-1, (non-utf8), and decoded fine, on both TB68 and
    TB24/Enigma as well.

    The only messages that fail originate from TB68/Enigmail when using
    utf-8 in this echo.

    I doubt that JamNNTPd has anything to do with munging the messages
    because it is happening in email originating from the TB68 system too!
    :( A recent email that I accidentally sent as text/plain; charset=windows-1252, failed too.

    Maybe the default "View incoming as" and "Write outgoing as" settings
    may be doing some overrides? Or.. would the fonts that I use to VIEW
    have something to do with it?

    On the other hand, outbound signed clear-text iso-8859-1 from the TB24
    (this message) is behaving nicely in this echo and email.

    This seems to be a weakness in the signed clear-text process when one is
    not mindful of the charset that is in use.


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

    iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl4veM4ACgkQ7w6JZVeJ WJt9wwf9Fp8aGcKMt6f+Vos12+NHo1h2PY5EMuquetCz6st1wbOH0nE1bMSVNCFc QhQaW0IJkKZayeHaF9ne1JnYoDMHY3FGfw79Paz+tbancaXeaUSR38YxXX3R4tdT YUmZv8+W/vqa9vTfUjzvo5Q6SpjU4BKMkTq3lgkrF3NQIInzNTUxdtik1enBlu6p dSx1iucqv0ZFgRMN0dK5ABLTSrOLPlEutvAgjXTR1DsR4eK5J1RifNhTBMl5C36d 6pMJYgLBHZrVIM4taifFaWId0e1ayJs6kOFhDcU4MNL0m5JEt6s9iCrrfZFjvnXB GyWDTWHPodbYVqlY07VZ8En7icl3+A==
    =GDMW
    -----END PGP SIGNATURE-----

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