Subj : Re: Decoding this...
To : Vk3jed
From : Bbsing.Bbs
Date : Wed Jul 31 2019 09:24 pm
-=> Vk3jed wrote to Bbsing.Bbs <=-
Bb> Perfect! It worked.
Bb> BBS systems can have secure message communication! :)
Vk> Cool, what was the total process?
Sorry Vk, I went dark for awhile due to projects I was working on, and you may
have the process already.
Ah .. so if I can remember the total process...
Here is the general process.
make sure you have a pgp/gpg key, post your public key for the initial async
encryption ... this is the type where you receive someone's posted public key
and then add that to your keystore, then craft a message for that person's key.
Now if its just synchronous then... they've sent you a shared single key.
Here on the bbs or fido, .. other packet mails you can post the message using
gpg output of ascii armor ... which is basically clear text. This text you'll
also use to post your key but you can use binary formats. I like the armor text
style because its really versatil.
So if we were trading messages and we did not have a single shared key we would
use asynchronous encryption to trade the key, or via phone ... something like
that.
1) get gnupgp
2) create a private key 4096 bit
a) smaller key sizes allow for easier signature line use, but may cost
in compromised communicates if cracked.
3) output your public key to a file in armor text
4) place your public key in a signature line
5) anyone can get your public key and send you a private message that only you
can unlock.
openssl allows for armor text as well, but from the perspective of regular
message communications like this one, only synchronous encryption (shared key).
