Trying a signing again. Hopefully there won't be double spacing.
There is. :-(
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...
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.
-----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-----
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. :(
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
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
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.
| Sysop: | Coz |
|---|---|
| Location: | Anoka, MN |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 24:32:26 |
| Calls: | 97 |
| Files: | 4,642 |
| Messages: | 217,167 |