On Monday 30 April 2018 13:17:43 Curt Howland wrote:
> On Mon, Apr 30, 2018 at 3:08 PM, Gene Heskett <gheskett@...> wrote:
> > On Monday 30 April 2018 11:27:58 Stefan Krusche wrote:
> >> You need to import the sender's public key.
> >
> > Is that buried in the kmail gpg menu's someplace? or a function of kgpg?
>
> kgpg reads your keyrings, so you can use kgpg to import the key, or
> gpg directly.
>
> However, Kmail does not like sending to or verifying with _untrusted_ keys.
>
> There is a "list untrusted keys" setting, but it's more reliable to
> trust those people's keys you get signed email from.
>
> One reason, maybe the primary reason, I use TDE is Kmail with mbox
> files which I can save, and search, with standard text tools, as well
> as easy gpg integration.
>
> Reading this thread, I, too, have been frustrated by the general lack
> of anyone caring about encrypting their email. I'm using the Gmail web
> interface right now, there used to be a Firefox plug-in which
> encrypted/signed Gmail, but the developer simply could not keep up
> with how often Google "updated" (read: changed) the interface and
> broke his plug-in.
>
> Curt-

Yeah, they read that Gmail is encrypted, or that this service now uses TLS as 
well as SSL, or that they offer this or that security feature, or promise 
more privacy; and then they think there is nothing more to do. 

Everybody talks about encryption, but not many actually use it. And you can 
see why here: because encrypting all alone is like having sex all alone. 
Unless you do it together with others, it's just wanking. 

Bill
Bill