From: Chris Knadle <Chris.Knadle@coredump.us>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Encrypted list
Date: Mon, 24 Mar 2014 19:19:21 +0000 [thread overview]
Message-ID: <4004025.G86uLotGlz@trelane> (raw)
In-Reply-To: <20140320184234.GG23804@szaflik.hasiok.net>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
On Monday, March 24, 2014 13:25:40 Patrice Levesque wrote:
> > Myself, I know only a handful of poeple that I can trust to hold their
> > mailbox secure... and even with them I don't use encrypted email just
> > because I don't have anything so sensitive to say, so it will be just
> > a hassle or a moslty pointless excercise of GPG skills.
>
> If I may add my 2 cents, encrypting regular non-sensitive mail does not
> appear pointless to me.
>
> For one thing it ensures that GPG mail setups are properly configured
> all the time and ready when needed for critical data.
>
> It also gives the intelligence agencies something bogus to chew on; let
> them waste resources deciphering cat pictures.
>
> Lastly, the current poor adoption rate of encryption makes every GPG'd
> mail stick out. Encrypting non-sensitive data lessens that effect.
Agree with this. For people I exchange encrypted email with (of which there
are very few), we've gone to encrypting 100% of our email exchanges, using the
same line of thinking as the above as to why.
However; none of the (many) email lists I'm on use GPG encryption, a few of
them use TLS for MTA transfers but several others have purposely are set not
to use TLS. [The mailing lists I'm deploying use TLS transfers if available.]
As a thought experiment, let's say that we had an opportunity to "design the
world of all of our friends' email". What would that look like?
For starters, all email transfers would use TLS, and all of our friends would
be using "private" mail servers rather than 3rd party services like Gmail.
GPG is too complicated for most of them to use, so we know most of them won't.
The end result is that mail stored on the private servers and our local hard
disks isn't encrypted -- with some difficulty the latter part is fixable
though.
As such, putting some effort wards encrypting our own filesystems seems like a
worthwhile effort.
-- Chris
--
Chris Knadle
Chris.Knadle@coredump.us
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-24 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 18:42 [mlmmj] Encrypted list Piotr Auksztulewicz
2014-03-20 21:34 ` Matti Nykyri
2014-03-20 23:31 ` Chris Knadle
2014-03-21 15:48 ` Matti Nykyri
2014-03-21 20:09 ` Chris Knadle
2014-03-22 7:40 ` Matti Nykyri
2014-03-22 20:38 ` Chris Knadle
2014-03-24 16:49 ` Piotr Auksztulewicz
2014-03-24 17:25 ` Patrice Levesque
2014-03-24 19:19 ` Chris Knadle [this message]
2014-03-24 20:32 ` Ben Schmidt
2014-03-24 23:05 ` Chris Knadle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4004025.G86uLotGlz@trelane \
--to=chris.knadle@coredump.us \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox