Commit 76a4547f authored by intrigeri's avatar intrigeri
Browse files

We should not write to the list.

List subscribers risk replying to the list instead of (or in addition to) to
tails@, which would violate "Unless you really want to start the key revocation
process, do not write to this mailing list".

I'd rather not rely only on a big fat warning to avoid that, while we
have a simple solution to lower the risk significantly.
parent c2c4e668
......@@ -247,8 +247,8 @@ At least every 2 years, we make sure that the mechanism still works:
1. We review internally the list of members of each group and decide
possible additions to, and removals from, each group.
1. We write to the list to ask all members to check that they still have
their share and the number in the file name.
1. We write to every individual member of each group to ask them to check
that they still have their share and the number in the file name.
<pre>
Subject: update
......@@ -259,7 +259,7 @@ Some years ago, you agreed to be part of a distributed mechanism for the
revocation certificate of the Tails signing key and we sent you a
cryptographic share of this revocation certificate.
Today, we are asking each of you to:
Today, we are asking you to:
1. Verify that this email is signed by the Tails signing key.
......@@ -272,8 +272,6 @@ Today, we are asking each of you to:
- The number NNN in the file name of your share.
/!\ Please confirm us on tails@boum.org and not on this list. /!\
For the record, the address of the mailing list that you should write to
in case you want to assemble the revocation certificate is:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment