1. Forum
  2. FidoNet Areas
  3. PUBLIC KEYS

  • bad crc?

    From August Abolins@2:221/360 to All on Thu Jun 18 00:58:11 2020
    -----BEGIN PGP SIGNED MESSAGE-----

    Hash: SHA256



    This one should be signed with a new "fido" signature.

    NOT using utf-8 with this one.


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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEEJ6dHnJksyz/l6Pv4SI2tEBBS3ZMFAl7qkfMACgkQSI2tEBBS

    3ZMukgf/Q1jd+u8HlQeJAjYfslg3HllO7i3KFT5dYh4Fk5xtgLw5ScBa4ALQM8Dn

    +WeuuW9aSTF8KMbX6M1Zj64JeerxrXFFB7mnmIj0nPVne+QASK9ITmx2N+jQEs1M

    O+cUUU8XJ4TA8o6I6BQx0ciCw3aldjMkSQ2iSNF6YYRg+ZTeTCXReN5JhyE0tmOD

    VNh7kedXuLWrhWqOYotK5eXHn/26IW/ZdWK6yvTQ1FGi/Nv6RO4fUaghDR+Owl9Q

    VaPL45kYTjwOrI/c4jXOwazn9OQDQwkh8s6HRUYa+oIFMBYFJKPunKnCNOEk4MBW

    8vBpww8lkwUJqvahNry2FIuS6WZpaA==

    =OYLt

    -----END PGP SIGNATURE-----

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Sean Rima@2:263/1.1 to August Abolins on Thu Jun 18 03:05:22 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA512


    Hello August!

    18 Jun 20 00:58, you wrote to all:

    -----BEGIN PGP SIGNED MESSAGE-----

    Hash: SHA256



    This one should be signed with a new "fido" signature.

    NOT using utf-8 with this one.


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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEEJ6dHnJksyz/l6Pv4SI2tEBBS3ZMFAl7qkfMACgkQSI2tEBBS

    3ZMukgf/Q1jd+u8HlQeJAjYfslg3HllO7i3KFT5dYh4Fk5xtgLw5ScBa4ALQM8Dn

    +WeuuW9aSTF8KMbX6M1Zj64JeerxrXFFB7mnmIj0nPVne+QASK9ITmx2N+jQEs1M

    O+cUUU8XJ4TA8o6I6BQx0ciCw3aldjMkSQ2iSNF6YYRg+ZTeTCXReN5JhyE0tmOD

    VNh7kedXuLWrhWqOYotK5eXHn/26IW/ZdWK6yvTQ1FGi/Nv6RO4fUaghDR+Owl9Q

    VaPL45kYTjwOrI/c4jXOwazn9OQDQwkh8s6HRUYa+oIFMBYFJKPunKnCNOEk4MBW

    8vBpww8lkwUJqvahNry2FIuS6WZpaA==

    =OYLt

    -----END PGP SIGNATURE-----

    The spacing killed the message. Is your key on a server ?

    Sean


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

    iQEzBAEBCgAdFiEE8alTjFdiqHf/9xvIdtqljnTz/qAFAl7qzBIACgkQdtqljnTz /qA0zgf/SR2dNQn2PPfJUyUzYLMDKrluhXkaANbLD9YYBzHSaH3JK36rPB1eggY3 G51yg37FaPsfETs1o2YkbEeirkLSiZiPSa0EG5i9fBO0gWAcr53i5PY3RA69VI9h k+CYMY85zJjMUUTW1T4BKVi2jUVZYco742A9fv0R/ZPmbtghzWqupW3cUJyWkPVH SXAZxf5zJ+BDvS5yWDHl/bRgQPgUM5AEWPiA5MMOLdIVlDZWywcnE02SHsiofVuY TaCXRfAnoFxCxRDqtpJxTzqpzuvRxvfbozdBFvnbc3Wpo9n5gzCDLWmSBh1D8t7g l3vAUz4djBgHcdq/2BNpPmHs3Cdj9Q==
    =6cgP
    -----END PGP SIGNATURE-----
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: A Pointless Point in Connemara (2:263/1.1)
  • From August Abolins@2:221/1.58 to Sean Rima on Wed Jun 17 22:33:00 2020
    Hello Sean!

    ** On Thursday 18.06.20 - 03:05, Sean Rima wrote to August Abolins:

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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEEJ6dHnJksyz/l6Pv4SI2tEBBS3ZMFAl7qkfMACgkQSI2tEBBS

    3ZMukgf/Q1jd+u8HlQeJAjYfslg3HllO7i3KFT5dYh4Fk5xtgLw5ScBa4ALQM8Dn



    The spacing killed the message. Is your key on a server ?


    The double-spacing was a total surprise. I have no idea why that
    happened.

    I have a key published in PKEY_DROP, and should be available on a server
    of your choice. The key ID is in the Origin line of this message.


    ../|ug

    --- OpenXP 5.0.44
    * Origin: Key ID = 0x5789589B (2:221/1.58)
  • From August Abolins@2:221/360 to Sean Rima on Thu Jun 18 05:36:43 2020
    -----BEGIN PGP SIGNED MESSAGE-----

    Hash: SHA256



    On 6/17/2020 10:05 PM, between "Sean Rima : August Abolins":

    8vBpww8lkwUJqvahNry2FIuS6WZpaA==

    =OYLt

    -----END PGP SIGNATURE-----

    The spacing killed the message. Is your key on a server ?

    Trying a signing again. Hopefully there won't be double spacing.




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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEEJ6dHnJksyz/l6Pv4SI2tEBBS3ZMFAl7q0y8ACgkQSI2tEBBS

    3ZO66QgAkRVIy2nW9efC6ZW1M/Mkncit0MBuUFjydi0ZfZveXs//6DB2iL0SfgY7

    F+bHCckhZ3wV1H7VnbJlnFwqRIdvGuxjD45p73m9obiiUgZqiKA/G/uy2+XziHas

    lz1hYo/WaDtywII4zOud+7LTMJgH6EAPu6DXiv3jQEIDoo+ndYyZxuBDgZIR+DWU

    qOA3Xv7/DMaKqK8Zcg+uG6FKIc9STfKr8ANJgnh+6FUhPXdT9s4/T/nlwADmbzrc

    ZDICSJVLdLV9zPSBmNizHN04KhEerr+KV5XvKwyWbGv/yajdOITiA10rbPIM5QR4

    Ds2ovM5eBgKBqRGyS3za1yA3ebTusA==

    =DLsk

    -----END PGP SIGNATURE-----

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Sean Rima@2:263/1.1 to August Abolins on Thu Jun 18 03:43:36 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA512


    Hello August!

    18 Jun 20 00:58, you wrote to all:

    This one should be signed with a new "fido" signature.

    NOT using utf-8 with this one.

    when I did gpg --verify on the message I got :

    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)
    gpg: not a detached signature
    gpg: no signature found
    gpg: the signature could not be verified.
    Please remember that the signature file (.sig or .asc)
    should be the first file given on the command line.



    Sean


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

    iQEzBAEBCgAdFiEE8alTjFdiqHf/9xvIdtqljnTz/qAFAl7q1Q8ACgkQdtqljnTz /qDXHQf/bqtI+PaPSP1V3CXMI6YRr1mPXagW00gY/BposwfDVL5Jyy80CSq6YQaq Gv1DSkH/rYSkHat/Vvf4xVT/S9/Uou4r8FpK8L080/rsMF6fAxUujBHel91bI16U w2I3YSx3oTh4K5x+iXevl9eV0yLGzgGlorpkPFEoAvnptLrULUsoq15vKAtQB6fS QVGN2VxzBf6dMELX5d9RpTGgFnt7zGVl+G+eHYJ3d9wvVV8RX8IhEWqOxyHTqxSS DcAWmZndvJY19hH58iPKg0yGSmQtDBGol/M0JHOiOfKaWCQeyBqTvy7KXcuD4FXA y2wyAkSHNGSR90+nA4vuDG/YhVU4lA==
    =u9ZO
    -----END PGP SIGNATURE-----
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: A Pointless Point in Connemara (2:263/1.1)
  • From August Abolins@2:221/360 to Sean Rima on Thu Jun 18 06:28:11 2020
    Hello Sean!

    ** On Thursday 18.06.20 - 03:43, Sean Rima wrote to August Abolins:
    ^^^^^

    That's almost 4am your local time?


    when I did gpg --verify on the message I got :

    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)
    gpg: not a detached signature
    gpg: no signature found
    gpg: the signature could not be verified.
    Please remember that the signature file (.sig or .asc)
    should be the first file given on the command line.

    Yes.. I'm getting the same thing after the message is posted:

    OpenPGP Security Info

    gpg command line and output:
    C:\Program Files\gnupg\bin\gpg.exe
    gpg: NOTE: you should run 'diskperf -y' to enable the disk statistics
    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)


    I don't know why this is happening. :(

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Thu Jun 18 09:30:01 2020
    Hi August,

    On 2020-06-18 05:36:43, you wrote to Sean Rima:

    @MSGID: 2:221/360.0 5eead338
    @REPLY: 2:263/1.1 5eeacc1c
    @PID: JamNNTPd/OS2 1.3 20200606
    @TID: GE/2 1.2
    @CHRS: CP437 2
    @TZUTC: 0300
    -----BEGIN PGP SIGNED MESSAGE-----

    Hash: SHA256



    On 6/17/2020 10:05 PM, between "Sean Rima : August Abolins":

    8vBpww8lkwUJqvahNry2FIuS6WZpaA==

    =OYLt

    -----END PGP SIGNATURE-----

    The spacing killed the message. Is your key on a server ?

    Trying a signing again. Hopefully there won't be double spacing.

    There is. :-(


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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEEJ6dHnJksyz/l6Pv4SI2tEBBS3ZMFAl7q0y8ACgkQSI2tEBBS

    3ZO66QgAkRVIy2nW9efC6ZW1M/Mkncit0MBuUFjydi0ZfZveXs//6DB2iL0SfgY7

    F+bHCckhZ3wV1H7VnbJlnFwqRIdvGuxjD45p73m9obiiUgZqiKA/G/uy2+XziHas

    lz1hYo/WaDtywII4zOud+7LTMJgH6EAPu6DXiv3jQEIDoo+ndYyZxuBDgZIR+DWU

    qOA3Xv7/DMaKqK8Zcg+uG6FKIc9STfKr8ANJgnh+6FUhPXdT9s4/T/nlwADmbzrc

    ZDICSJVLdLV9zPSBmNizHN04KhEerr+KV5XvKwyWbGv/yajdOITiA10rbPIM5QR4

    Ds2ovM5eBgKBqRGyS3za1yA3ebTusA==

    =DLsk

    -----END PGP SIGNATURE-----

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0) SEEN-BY: 154/10 203/0 221/0 1 6 360 229/101 240/5832 280/464 5003 288/100 SEEN-BY: 292/854 8125 310/31 396/45 423/81 120 712/848 770/1 2452/250 @PATH: 221/360 1 280/464

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Thu Jun 18 09:37:53 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA256

    Hi Sean,

    On 2020-06-18 03:43:36, you wrote to August Abolins:

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA512


    Hello August!

    18 Jun 20 00:58, you wrote to all:

    This one should be signed with a new "fido" signature.

    NOT using utf-8 with this one.

    when I did gpg --verify on the message I got :

    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)
    gpg: not a detached signature
    gpg: no signature found
    gpg: the signature could not be verified.
    Please remember that the signature file (.sig or .asc)
    should be the first file given on the command line.



    Sean


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

    iQEzBAEBCgAdFiEE8alTjFdiqHf/9xvIdtqljnTz/qAFAl7q1Q8ACgkQdtqljnTz /qDXHQf/bqtI+PaPSP1V3CXMI6YRr1mPXagW00gY/BposwfDVL5Jyy80CSq6YQaq Gv1DSkH/rYSkHat/Vvf4xVT/S9/Uou4r8FpK8L080/rsMF6fAxUujBHel91bI16U w2I3YSx3oTh4K5x+iXevl9eV0yLGzgGlorpkPFEoAvnptLrULUsoq15vKAtQB6fS QVGN2VxzBf6dMELX5d9RpTGgFnt7zGVl+G+eHYJ3d9wvVV8RX8IhEWqOxyHTqxSS DcAWmZndvJY19hH58iPKg0yGSmQtDBGol/M0JHOiOfKaWCQeyBqTvy7KXcuD4FXA y2wyAkSHNGSR90+nA4vuDG/YhVU4lA==
    =u9ZO
    -----END PGP SIGNATURE-----

    Good signature:

    wilfred@wilnux5:~> gpg --verify sr.msg
    gpg: Signature made Thu 18 Jun 2020 04:44:31 AM CEST using RSA key ID 74F3FEA0 gpg: checking the trustdb
    gpg: public key FBBB8AB1 is 58138 seconds newer than the signature
    gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
    gpg: depth: 0 valid: 6 signed: 4 trust: 0-, 0q, 0n, 0m, 0f, 6u
    gpg: depth: 1 valid: 4 signed: 0 trust: 2-, 0q, 0n, 1m, 1f, 0u
    gpg: next trustdb check due at 2021-11-12
    gpg: Good signature from "Sean Rima <sean@rima.ie>" [unknown]
    gpg: aka "Sean Rima <thecivvie@gmail.com>" [unknown]
    gpg: aka "Sean Rima <seanrima@icloud.com>" [unknown]
    gpg: aka "Sean Rima (iCloud) <seanrima@icloud.com>" [unknown] gpg: WARNING: This key is not certified with a trusted signature!
    gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F1A9 538C 5762 A877 FFF7 1BC8 76DA A58E 74F3 FEA0


    Bye, Wilfred.

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

    iQIcBAEBCAAGBQJe6xnPAAoJEDuzfahKl5MrneQQAK9ssL86mt8daA/TNw6UwJYp AnstWZW3XnngQLJGNKwIO0sreOf3EkfTLehI90YPODYKSkM2sfgPtafwRi3y72HC 0OX96rOFw3e6osEfXDzY9RCJb0C7w1LHs08QCiz2cSke4shfBivbQUyuqxgdZamv 0Jo5UyCuDl0gxStVBkxXC5i1kmx0l/WkF6JhuvsML1hnBzioE+xFnMpaPK2Ow15k qMF5vwex3o8yRUgJEaTafvL7bZEnF+e4hbd9YTn/WOt/PSmd4+cGEW+BLL/sJOHg RhldMbZ98WX/QVCyhqUeb631LJW4vjasREh/KezDZr49nQTEFuUuJ2BW+eWe4OJd 8yBhTBeghKkGHaWRdZdveFocj+cdp8e+WLGR/oHuyD4QO5Tz8SXS29rtHu6ZJRhT gtsqPWvKr7hHZxf/bGMWZvmdgfiJKkJXhZ0pft/ZuJ45Wva72RGDo5z6rfPtliew gill2uSg6g1ZPdFlSS1qTBMM51Muc6o+9q0qPOxu1jyc5ty0eDzJN0WpimwE9K9U wd0aNmKOlbc5LTgHnCKiDz6CyB4WY2VCW3YtZl549z6tzewSoUJ3rlRMjZsfvWAD Z8i7ekWA2siuJ+rY50V4cP3et4VTAbC4+nTFBRSZUSCs1Vz9wqHlRv2myGseYtQO pOXfMkoyYdfc9wmILodi
    =A/RI
    -----END PGP SIGNATURE-----
    --- 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 Thu Jun 18 16:20:39 2020
    -----BEGIN PGP SIGNED MESSAGE-----

    Hash: SHA256



    On 6/18/2020 3:30 AM, between "Wilfred van Velzen : August Abolins":


    Trying a signing again. Hopefully there won't be double spacing.

    There is. :-(


    THIS one should be normal. If so, I have the "secret".



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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl7raiAACgkQ7w6JZVeJ

    WJtk0Af+NB0JzpZqVv/HkfgtgPuwRAh5jJNyYDZ9WSoElh127XDHg53QsGHuakXl

    u/naAakKr5v4q+jX3YJ//yCDjrUqmtPn4aTb8FARSz0LydWUtKJ030ZVjwg8VF7x

    XGTY8L50oOb/RBlBzTRgm77LcHfAtdQ4IRZV3Y3tpK9xiFBxMUAginVM7NOiGGZa

    wEZC/79tTjxqjTui3spWvdlYXRUmx6KrFj8L7Jsu9CarlnsvRawDFbUIxyDJW0Ij

    fHTKA76hJBZN4ZmnPk6syXERtXapZ0beA8IHiHyHhyf++1HdxpujLYOLkAeXU3kx

    f/RVtwXnld0rGISQ+XGjuGyJm7UvUw==

    =nXLf

    -----END PGP SIGNATURE-----

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Wilfred van Velzen@2:280/464 to August Abolins on Thu Jun 18 15:43:07 2020
    Hi August,

    On 2020-06-18 16:20:39, you wrote to me:

    @MSGID: 2:221/360.0 5eeb6a1e
    @REPLY: 2:280/464 5eeb1804
    @PID: JamNNTPd/OS2 1.3 20200606
    @TID: GE/2 1.2
    @CHRS: CP437 2
    @TZUTC: 0300
    -----BEGIN PGP SIGNED MESSAGE-----

    Hash: SHA256



    On 6/18/2020 3:30 AM, between "Wilfred van Velzen : August Abolins":


    Trying a signing again. Hopefully there won't be double spacing.

    There is. :-(


    THIS one should be normal. If so, I have the "secret".

    Nope...


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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEE0OsqKVIE8xZ+slA87w6JZVeJWJsFAl7raiAACgkQ7w6JZVeJ

    WJtk0Af+NB0JzpZqVv/HkfgtgPuwRAh5jJNyYDZ9WSoElh127XDHg53QsGHuakXl

    u/naAakKr5v4q+jX3YJ//yCDjrUqmtPn4aTb8FARSz0LydWUtKJ030ZVjwg8VF7x

    XGTY8L50oOb/RBlBzTRgm77LcHfAtdQ4IRZV3Y3tpK9xiFBxMUAginVM7NOiGGZa

    wEZC/79tTjxqjTui3spWvdlYXRUmx6KrFj8L7Jsu9CarlnsvRawDFbUIxyDJW0Ij

    fHTKA76hJBZN4ZmnPk6syXERtXapZ0beA8IHiHyHhyf++1HdxpujLYOLkAeXU3kx

    f/RVtwXnld0rGISQ+XGjuGyJm7UvUw==

    =nXLf

    -----END PGP SIGNATURE-----

    --- Thunderbird 2.0.0.24 (Windows/20100228)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0) SEEN-BY: 154/10 203/0 221/0 1 6 360 229/101 240/5832 280/464 5003 288/100 SEEN-BY: 292/854 8125 310/31 396/45 423/81 120 712/848 770/1 2452/250 @PATH: 221/360 1 280/464

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From August Abolins@2:221/1.58 to Wilfred van Velzen on Thu Jun 18 09:49:00 2020
    Hello Wilfred!

    ** On Thursday 18.06.20 - 15:43, Wilfred van Velzen wrote to August Abolins:

    Trying a signing again. Hopefully there won't be double spacing.

    There is. :-(


    THIS one should be normal. If so, I have the "secret".

    Nope...



    Thank for the confirmation. It even looks bad in OpenXP. WTF.



    ../|ug

    --- OpenXP 5.0.44
    * Origin: Key ID = 0x5789589B (2:221/1.58)
  • From Sean Rima@2:263/1 to August Abolins on Tue Jun 23 00:10:08 2020

    Hello August!

    17 Jun 20 22:33, you wrote to me:

    Hello Sean!

    ** On Thursday 18.06.20 - 03:05, Sean Rima wrote to August Abolins:

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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEEJ6dHnJksyz/l6Pv4SI2tEBBS3ZMFAl7qkfMACgkQSI2tEBBS

    3ZMukgf/Q1jd+u8HlQeJAjYfslg3HllO7i3KFT5dYh4Fk5xtgLw5ScBa4ALQM8Dn



    The spacing killed the message. Is your key on a server ?


    The double-spacing was a total surprise. I have no idea why that happened.

    I have a key published in PKEY_DROP, and should be available on a
    server of your choice. The key ID is in the Origin line of this message.

    I am subscribed so will grab it when I see it

    Sean


    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: A Destination in the Sun (2:263/1)
  • From Sean Rima@2:263/1 to August Abolins on Tue Jun 23 00:10:34 2020

    Hello August!

    18 Jun 20 05:36, you wrote to me:

    -----BEGIN PGP SIGNED MESSAGE-----

    Hash: SHA256



    On 6/17/2020 10:05 PM, between "Sean Rima : August Abolins":

    8vBpww8lkwUJqvahNry2FIuS6WZpaA==

    =OYLt

    -----END PGP SIGNATURE-----

    The spacing killed the message. Is your key on a server ?

    Trying a signing again. Hopefully there won't be double spacing.




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

    Comment: A book fell on my head. I only have my shelf to blame.



    iQEzBAEBCAAdFiEEJ6dHnJksyz/l6Pv4SI2tEBBS3ZMFAl7q0y8ACgkQSI2tEBBS

    3ZO66QgAkRVIy2nW9efC6ZW1M/Mkncit0MBuUFjydi0ZfZveXs//6DB2iL0SfgY7

    F+bHCckhZ3wV1H7VnbJlnFwqRIdvGuxjD45p73m9obiiUgZqiKA/G/uy2+XziHas

    lz1hYo/WaDtywII4zOud+7LTMJgH6EAPu6DXiv3jQEIDoo+ndYyZxuBDgZIR+DWU

    qOA3Xv7/DMaKqK8Zcg+uG6FKIc9STfKr8ANJgnh+6FUhPXdT9s4/T/nlwADmbzrc

    ZDICSJVLdLV9zPSBmNizHN04KhEerr+KV5XvKwyWbGv/yajdOITiA10rbPIM5QR4

    Ds2ovM5eBgKBqRGyS3za1yA3ebTusA==

    =DLsk

    -----END PGP SIGNATURE-----

    Double spaced again

    Sean


    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: A Destination in the Sun (2:263/1)
  • From Sean Rima@2:263/1 to August Abolins on Tue Jun 23 00:11:30 2020

    Hello August!

    18 Jun 20 06:28, you wrote to me:

    Hello Sean!

    ** On Thursday 18.06.20 - 03:43, Sean Rima wrote to August Abolins:
    ^^^^^

    That's almost 4am your local time?


    when I did gpg --verify on the message I got :

    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)
    gpg: not a detached signature
    gpg: no signature found
    gpg: the signature could not be verified.
    Please remember that the signature file (.sig or .asc)
    should be the first file given on the command line.

    Yes.. I'm getting the same thing after the message is posted:

    OpenPGP Security Info

    gpg command line and output:
    C:\Program Files\gnupg\bin\gpg.exe
    gpg: NOTE: you should run 'diskperf -y' to enable the disk
    statistics
    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)


    I don't know why this is happening. :(

    TB is dropping support for GPG or something so maybe that is affect it

    Sean


    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: A Destination in the Sun (2:263/1)
  • From Sean Rima@2:263/1 to Wilfred van Velzen on Tue Jun 23 00:12:28 2020

    Hello Wilfred!

    18 Jun 20 09:37, you wrote to me:

    Hello August!

    18 Jun 20 00:58, you wrote to all:

    This one should be signed with a new "fido" signature.

    NOT using utf-8 with this one.

    when I did gpg --verify on the message I got :

    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)
    gpg: not a detached signature
    gpg: no signature found
    gpg: the signature could not be verified.
    Please remember that the signature file (.sig or .asc)
    should be the first file given on the command line.



    Sean


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

    iQEzBAEBCgAdFiEE8alTjFdiqHf/9xvIdtqljnTz/qAFAl7q1Q8ACgkQdtqljnTz
    /qDXHQf/bqtI+PaPSP1V3CXMI6YRr1mPXagW00gY/BposwfDVL5Jyy80CSq6YQaq
    Gv1DSkH/rYSkHat/Vvf4xVT/S9/Uou4r8FpK8L080/rsMF6fAxUujBHel91bI16U
    w2I3YSx3oTh4K5x+iXevl9eV0yLGzgGlorpkPFEoAvnptLrULUsoq15vKAtQB6fS
    QVGN2VxzBf6dMELX5d9RpTGgFnt7zGVl+G+eHYJ3d9wvVV8RX8IhEWqOxyHTqxSS
    DcAWmZndvJY19hH58iPKg0yGSmQtDBGol/M0JHOiOfKaWCQeyBqTvy7KXcuD4FXA
    y2wyAkSHNGSR90+nA4vuDG/YhVU4lA==
    =u9ZO
    -----END PGP SIGNATURE-----

    Good signature:

    wilfred@wilnux5:~> gpg --verify sr.msg
    gpg: Signature made Thu 18 Jun 2020 04:44:31 AM CEST using RSA key ID 74F3FEA0
    gpg: checking the trustdb
    gpg: public key FBBB8AB1 is 58138 seconds newer than the signature
    gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
    gpg: depth: 0 valid: 6 signed: 4 trust: 0-, 0q, 0n, 0m, 0f, 6u
    gpg: depth: 1 valid: 4 signed: 0 trust: 2-, 0q, 0n, 1m, 1f, 0u
    gpg: next trustdb check due at 2021-11-12
    gpg: Good signature from "Sean Rima <sean@rima.ie>" [unknown]
    gpg: aka "Sean Rima <thecivvie@gmail.com>" [unknown]
    gpg: aka "Sean Rima <seanrima@icloud.com>" [unknown]
    gpg: aka "Sean Rima (iCloud) <seanrima@icloud.com>" [unknown]
    gpg: WARNING: This key is not certified with a trusted signature!
    gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F1A9 538C 5762 A877 FFF7 1BC8 76DA
    A58E 74F3 FEA0

    Thanks, I have recently extended this key by a year. next year I will generate a new key on my Yubico Key


    Sean


    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: A Destination in the Sun (2:263/1)
  • From August Abolins@2:221/360 to Sean Rima on Tue Jun 23 16:26:26 2020
    On 6/22/2020 7:11 PM, between "Sean Rima : August Abolins":

    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)

    I don't know why this is happening. :(

    TB is dropping support for GPG or something so maybe that is affect it


    No, that's not it. I was operating a fine 2.0.0.24 version for years. No problem. I probably tinkered with TB's config editor too much. I have a few strategies in mind to prove it, and to maybe get back to 2.0.0.24. But I am a bit too saddened by the current brokenness.

    --- Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101125
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)
  • From Sean Rima@2:263/1 to August Abolins on Tue Jun 23 22:44:36 2020

    Hello August!

    23 Jun 20 16:26, you wrote to me:

    On 6/22/2020 7:11 PM, between "Sean Rima : August Abolins":

    gpg: invalid radix64 character 3A skipped
    gpg: invalid radix64 character 2E skipped
    gpg: invalid radix64 character 2E skipped
    gpg: CRC error; 750A9B - 3982ED
    gpg: [don't know]: invalid packet (ctb=0a)

    I don't know why this is happening. :(

    TB is dropping support for GPG or something so maybe that is
    affect it


    No, that's not it. I was operating a fine 2.0.0.24 version for years.
    No problem. I probably tinkered with TB's config editor too much. I
    have a few strategies in mind to prove it, and to maybe get back to 2.0.0.24. But I am a bit too saddened by the current brokenness.

    Ah ok, it is weird then that it suddenly changed

    Sean


    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: A Destination in the Sun (2:263/1)