From: Greg Farough <gregf@fsf.org>
To: libreplanet-discuss <libreplanet-discuss@libreplanet.org>
Subject: Updates to the Email Self-Defense Guide
Date: Tue, 13 Jul 2021 18:28:40 -0400 [thread overview]
Message-ID: <875yxddf1j.fsf@fsf.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 567 bytes --]
Hi, everyone,
Just writing to share with you that we've brought the often imitated,
never duplicated Email Self-Defense Guide up to date with another
round of edits. Please have a look and, ideally, introduce the Guide
to someone who doesn't already use GPG or email encryption to run
through it, helping their freedom and privacy at the same time.
<https://emailselfdefense.fsf.org/>
Exuberant encrypting,
-g
--
Greg Farough // Campaigns Manager
Free Software Foundation
Join the FSF and help us defend software freedom: https://my.fsf.org
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
reply other threads:[~2021-07-13 22:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yxddf1j.fsf@fsf.org \
--to=gregf@fsf.org \
--cc=libreplanet-discuss@libreplanet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).