Hi August,

On 2020-01-09 23:35:38, you wrote to me:

 >> Below is my reply to your message. It's not encrypted only signed (but
 >> not clearsigned). Anyone with gpg can decode it and view it's contents.
 >> If they have my public key they can verify it was me who wrote it. Why
 >> you would want to do it this way, I don't know. I can't think of a
 >> use-case for it...

 AA> TB decrypted it automatically, (but it obscured your preface above; the
 AA> decryption result in TB fills the whole reading window of the open
 AA> message).

I get the same thing when I decode a message with mixed content from within
golded. It's to be expected. But golded doesn't decode unless told to, so I
always see the mixed content first...

 AA> It contained this security header info:

 AA> Part of the message signed Good signature from Wilfred van Velzen
 AA>  Key ID: 0xD50ECD4F514B75DC0A064F893BB37DA84A97932B
 AA> / Signed on: 01/09/20, 3:58 PM Key fingerprint: D50E CD4F 514B 75DC 0A06
 AA> 4F89 3BB3 7DA8 4A97 932B Used Algorithms: RSA and SHA-1

Good.

 AA> I assume that it can then be read by anyone who has the key of the
 AA> author.  ?

No you don't even need the key, to decode it, only to verify it.

 AA> If so, then a good practical use would be if you wanted a totally
 AA> obscured message stream by adding an extra layer of frustration to just
 AA> anyone, or even from the bots that skim messages. ?  I kinda like that.

 AA> It would force the would-be reader to collect the keys of everyone who
 AA> is writing the messages, but still remain a lurker. ?

It doesn't work that way.

 AA> Not good good for sharing sensitive info though.

Nope. And it wasn't intended for that purpose.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815