-----BEGIN PGP PUBLIC KEY BLOCK-----
# gpg -k tommi
pub 1024R/2442E762 2015-11-20 [expires: 2027-10-18]
uid [ unknown] Tommi Koivula <sysop@rbb.bbs.fi>
sub 1024R/B8627807 2015-11-20 [expires: 2027-10-18]
pub 4096R/56CDF35B 2017-10-27 [expires: 2067-10-15]
uid [ unknown] Tommi Koivula <tommi@rbb.fidonet.fi>
uid [ unknown] Tommi Koivula <tommi@fidonet.fi>
sub 4096R/3ECEC94C 2017-10-27 [expires: 2067-10-15]
You intend to get (very) old!? ;)
If you send me your key finger print through another channel (we have exchanged emails in the past), I'll sign your key.
# gpg -k tommi
pub 1024R/2442E762 2015-11-20 [expires: 2027-10-18]
uid [ unknown] Tommi Koivula <sysop@rbb.bbs.fi>
sub 1024R/B8627807 2015-11-20 [expires: 2027-10-18]
pub 4096R/56CDF35B 2017-10-27 [expires: 2067-10-15]
uid [ unknown] Tommi Koivula <tommi@rbb.fidonet.fi>
uid [ unknown] Tommi Koivula <tommi@fidonet.fi>
sub 4096R/3ECEC94C 2017-10-27 [expires: 2067-10-15]
You intend to get (very) old!? ;)
2067 I will be 100 years old, I'll revoke the key then. :D
If you send me your key finger print through another channel (we have
exchanged emails in the past), I'll sign your key.
Ok, crashmail might be safe enough for fido address. :)
Ok, crashmail might be safe enough for fido address. :)
That's for me to decide, if I have enough trust in that the key and fingerprint came from the person who claims to have send them. ;)
Someone who can forge an echomail, can likely also forge a crashmail. But it might be harder to also forge the email address we previously used to communicate (and know my email address that was used).
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That's for me to decide, if I have enough trust in that the key and
fingerprint came from the person who claims to have send them. ;)
Someone who can forge an echomail, can likely also forge a crashmail.
But it might be harder to also forge the email address we previously
used to communicate (and know my email address that was used).
You're right, in real life this is all true, but in fidonet... :)
- ---
* Origin: telnet://v6.fidonet.fi (2:221/1)
-----BEGIN PGP SIGNATURE-----
iQEcBAEBAgAGBQJZ9dORAAoJEHsmq0n9rVPIYmQH/2c6w6FgyofpZJGEnQrOGZdy t+riwqpgeVFKRLlcNwGxbiw/WoZ2NeuGSYrNdJ7HPCwy+roxomiDQmJ/oIKEIpCx cPNdYqLvtmbOr5ycHgRdMO6e41xnW+3Ar5thk2Df1p90opgqI1WyyZS0QbdWB6EL 27EpXHwz3w8ufmTNjE0PvT9MiYbycYTO7xMh7YPJa+ON222orBVBLz7lufjjPTjf 77xKmC8LJQCBFSbAIjp9PLs4/gPufSBlex/6+FU2YZs487R8Nh5xsgdmWWH+ObTt zLeq6cjJu4wWvzojN0NoJENcSsu/N8UZMC0Pt6szCeflHG4e4uWBuv4FYVnRxW4=
=1UU/
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
iQEcBAEBAgAGBQJZ9dORAAoJEHsmq0n9rVPIYmQH/2c6w6FgyofpZJGEnQrOGZdy
t+riwqpgeVFKRLlcNwGxbiw/WoZ2NeuGSYrNdJ7HPCwy+roxomiDQmJ/oIKEIpCx
cPNdYqLvtmbOr5ycHgRdMO6e41xnW+3Ar5thk2Df1p90opgqI1WyyZS0QbdWB6EL
27EpXHwz3w8ufmTNjE0PvT9MiYbycYTO7xMh7YPJa+ON222orBVBLz7lufjjPTjf
77xKmC8LJQCBFSbAIjp9PLs4/gPufSBlex/6+FU2YZs487R8Nh5xsgdmWWH+ObTt
zLeq6cjJu4wWvzojN0NoJENcSsu/N8UZMC0Pt6szCeflHG4e4uWBuv4FYVnRxW4=
=1UU/
-----END PGP SIGNATURE-----
This is a signature made with a key you haven't published before?
gpg: Signature made zo 29 okt 2017 14:11:45 CET using RSA key ID FDAD53C8
And you won't send me the email... Now I'm getting suspicious! ;)
I'm cleaning up my key files... I now have two set up in this GoldED:
EXTERNUTIL 1 gpg.exe -o @file -u "sysop@rbb.bbs.fi" --clearsign @tmpfile EDITSAVEUTIL 1 "S gpg Sign the msg"
EXTERNUTIL 2 gpg.exe -o @file -u "tommi@fidonet.fi" --clearsign @tmpfile EDITSAVEUTIL 2 "p gpg sign the msg tommi@fidonet.fi"
I should remove one.:)
Email on the way, BTW.
EXTERNUTIL 1 gpg.exe -o @file -u "sysop@rbb.bbs.fi" --clearsign
@tmpfile
I have to think of a way how to incorporate that in my golded. The problem is I'm running golded as user 'fido' not as 'wilfred' ...
On 2017-10-30 14:13:41, I wrote to you:'fido'
EXTERNUTIL 1 gpg.exe -o @file -u "sysop@rbb.bbs.fi" --clearsign
@tmpfile
I have to think of a way how to incorporate that in my golded. The
problem is I'm running golded as user 'fido' not as 'wilfred' ...
I did it. It took some time to get it right. It involves creating a tmp file writable by both 'fido' and 'wilfred'. Setting /etc/sudoers, so
can call gpg for user 'fido' and a bash script to tie it all together.
EXTERNUTIL 1 gpg.exe -o @file -u "sysop@rbb.bbs.fi" --clearsign
@tmpfile
I have to think of a way how to incorporate that in my golded. The
problem is I'm running golded as user 'fido' not as 'wilfred' ...
I did it. It took some time to get it right. It involves creating a
tmp file writable by both 'fido' and 'wilfred'. Setting /etc/sudoers,
so 'fido' can call gpg for user 'fido' and a bash script to tie it
all together.
:-)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Tommi,
On 2017-10-31 12:49:17, you wrote to me:
EXTERNUTIL 1 gpg.exe -o @file -u "sysop@rbb.bbs.fi"
--clearsign @tmpfile
I have to think of a way how to incorporate that in my golded.
The problem is I'm running golded as user 'fido' not as
'wilfred' ...
I did it. It took some time to get it right. It involves
creating a tmp file writable by both 'fido' and 'wilfred'.
Setting /etc/sudoers, so 'fido' can call gpg for user 'fido'
and a bash script to tie it all together.
:-)
But did you check my signature on the message?
(And/or this one)
:-)
But did you check my signature on the message?
But did you check my signature on the message?
gpg --verify tmp
gpg: Signature made Mon Oct 30 22:09:20 2017 FLEST using RSA key ID 4A97932B
gpg: Good signature from "Wilfred van Velzen <wvvelzen@gmail.com>"
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 513 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 07:36:11 |
| Calls: | 8,287 |
| Calls today: | 4 |
| Files: | 15,517 |
| Messages: | 928,382 |
| Posted today: | 1 |