<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
  <file original="NoName" source-language="en" datatype="plaintext" target-language="ar">
    <body>
      <trans-unit xml:space="preserve" id="84400ff61f5990bd" weblate-flags="no-wrap">
        <source>[[!meta title="Revocation of the Tails signing key"]]
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="42428795aa64d66e">
        <source>This document proposes a mechanism for the distribution and activation of the revocation certificate of the Tails signing key.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="8950a2349e364c4b" weblate-flags="no-wrap">
        <source>Status</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9c6895d4c7218cb7">
        <source>This document is obsolete.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="77806af1777e6ffc">
        <source>It will be simplified or removed by [[!tails_gitlab tails/summit/-/issues/36]].</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="13619161b7da07f0" weblate-flags="no-wrap">
        <source>Goals</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="c08b92fdd58be235">
        <source>Covered by the current proposal:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="0a1d85dbc24daad9">
        <source>Prevent any single individual from revoking our signing key.</source>
        <target></target>
        <note from="developer">type: Bullet: '- '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="405d5ff6785e23b8">
        <source>Allow a coalition of people from the Board to revoke our signing key in case most of the people from the Board become unavailable.</source>
        <target></target>
        <note from="developer">type: Bullet: '- '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9b4600634cf7e3a2">
        <source>Allow a coalition of people, not necessarily from the Board, to revoke our signing key in case everybody or almost everybody from the Board becomes unavailable.</source>
        <target></target>
        <note from="developer">type: Bullet: '- '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="d5ea9625a30f58e2">
        <source>Make it hard for a coalition of people not from the Board to revoke our signing key unless everybody or almost everybody from the Board becomes unavailable.</source>
        <target></target>
        <note from="developer">type: Bullet: '- '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="845f88584cc002ea">
        <source>People not from the Board shouldn't know how the shares are spread and who has them.</source>
        <target></target>
        <note from="developer">type: Bullet: '- '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6ab86fa5bf655ab5">
        <source>People in possession of a share of the revocation certificate of the signing key should have instructions on how to use it if needed.</source>
        <target></target>
        <note from="developer">type: Bullet: '- '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="d32cb8a0b953c6cb" weblate-flags="no-wrap">
        <source>Groups</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="eacdd907e040a6cd">
        <source>We define four complementary groups of trusted people:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="bc38da7e157719e0">
        <source>Group A: people from the Board themselves</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6ce1fae0139e9c0a">
        <source>Group B</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="36db927129083f1a">
        <source>Group C</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="e23fa08d80f8dcd0">
        <source>Group D</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a356ba011b2cfa24">
        <source>All these people should have an OpenPGP key and understand what a revocation certificate is.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="100acca66c82c5dd" weblate-flags="no-wrap">
        <source>Cryptographic shares</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="82ff57e559601090">
        <source>We generate a revocation certificate of the signing key and split it into a number of cryptographic shares, using for example Shamir's secret sharing scheme implemented by `gfshare`.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="d4effff9167ce808">
        <source>The following combinations of people could get together and reassemble their shares to reconstruct a complete revocation certificate:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="26b59e752edbea33">
        <source>Three people from the Board: A{3}</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="f2cd184581a2d311">
        <source>Two people from the Board and one person not from the Board: A{2}+(B|C|D)</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="c9e9861526201488">
        <source>One person from the Board, and two people not from the Board but from two different groups: A+(B|C|D){2}</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="37199337843d5150">
        <source>Three people not from the Board but from three different groups: (B+C+D){3}</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="8630cc0eb9afa8dd">
        <source>We generate these shares:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="f7cd0a134ae6a40a">
        <source>N shares, one for each person from the Board</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9f3fd1df61371c7e">
        <source>1 share for people in group B</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9269a755b8a938f7">
        <source>1 share for people in group C</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a9d1290289309f48">
        <source>1 share for people in group D</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="4b8003b50b0d27e6" weblate-flags="no-wrap">
        <source>Who knows what</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="c8f3526ad8f1a953">
        <source>People from the Board know the composition of each group</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="56d794aa5a28796c">
        <source>People not from the Board:</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a6b072b52a1bf773">
        <source>Are explained in which circumstances they should revoke the signing key</source>
        <target></target>
        <note from="developer">type: Bullet: '    - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="e04e22baa0580769">
        <source>Are told to write to a certain contact email address if they decide to revoke the signing key</source>
        <target></target>
        <note from="developer">type: Bullet: '    - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="dc3a3c7fbe6db8c4">
        <source>Are told that they need three different shares to reassemble the revocation certificate</source>
        <target></target>
        <note from="developer">type: Bullet: '    - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="7887a8232dd67e90" weblate-flags="no-wrap">
        <source>Infrastructure</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="eddec5f625cf52ce">
        <source>Everybody who owns a share is subscribed to a mailing list.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="0b3a7cab8990b3f4">
        <source>This mailing list is hosted on a trusted server different from boum.org to be more resilient than our usual communication channels.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="b789c48f52852e16">
        <source>Someone hosting the mailing list is part of group B, C, or D so they can ensure that the list keeps working even if it never used.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9101b967382115e2" weblate-flags="no-wrap">
        <source>Changing the members of the groups B, C, or D</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="aba35e0554d22fe2">
        <source>To add someone to a given group:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="189a82cdad90f896">
        <source>Request someone from that group to send her share to the new person in the group.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="01192369385be013">
        <source>To remove someone from a given group:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="103968bc9da350ee">
        <source>Send new shares to everybody except to the person who is being removed.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="1ad642b0ccb91e18">
        <source>Request everybody to delete their previous share and track this.  Once everybody in 2 groups amongst B, C, or D have deleted their share, it becomes impossible for them to reassemble the revocation certificate with the previous set of shares.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="7c090cdd67f48dcc">
        <source>Let's hope that this doesn't happen very often :)</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="d4e29e41351721f3" weblate-flags="no-wrap">
        <source>Expiry</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="387de3269000a654">
        <source>There is no expiry date on revocation certificates. One way of cancelling the revocation power is to destroy all copies of shares of 2 groups amongst B, C, or D.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="70f74e19edd4f782" weblate-flags="no-wrap">
        <source><a id="invitation"/>
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="52b1ccde2ab7f953" weblate-flags="no-wrap">
        <source>Invitation email</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="4376b7c4f991634b">
        <source>Someone who has a personal trust relationship with the person being invited sends this email.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="7571885c7cd23249" weblate-flags="no-wrap">
        <source>&lt;pre&gt;
Subject: distribution
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6c8205819539a2f4">
        <source>Hi,</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="7500b0124eeb3e18">
        <source>We want to propose you to be part of a distributed mechanism for the revocation certificate of the Tails signing key.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9547cdd1f676c223">
        <source>The idea is to distribute cryptographic shares of this revocation certificate to people that we trust. These cryptographic shares can be put together to reassemble the revocation certificate and revoke the Tails signing key. This may be needed in case something really bad happens to us and we are not able to do the revocation ourselves.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="b2828af1e9f0f6e6">
        <source>Note: In all this document, 'us' refers to the Board.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="ccd9f02e97c2ec5f">
        <source>You can read a complete description of the distribution mechanism on:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="81e17d31867bd151">
        <source>https://tails.net/doc/about/openpgp_keys/signing_key_revocation.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="23c4850d3f0077d1">
        <source>The recipe is public and the only secret component is the list of people who are in possession of the cryptographic material.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="ccdc86e81e446dce">
        <source>We are proposing this to you because we trust in both your technical abilities to store your share in a safe place and manipulate it as required. But also because we trust you as a human being to make informed judgment on when to use your share and act only in the interest of Tails.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a23e6c3a271ae87f">
        <source>The bad things that could happen if the mechanism fails are:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="42a3bda20af1c071">
        <source>A. The signing key is not revoked when it should be. This could allow possible attackers to distribute malicious Tails images or publish malicious information on our name.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="eac502d02b12e977">
        <source>B. The signing key is revoked when it should not have been. This would prevent people from verifying our images with OpenPGP until we publish a new signing key and build trust in it.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="2661dc48e2f12e3a" weblate-flags="no-wrap">
        <source>Distribution of the shares</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9a09bbcd14eaa6a1">
        <source>Each person from the Board, group A, has a *different* share, A1, A2, ..., An.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="2fc9cd02a77bb435">
        <source>On top of this, we defined three complementary groups, B, C, and D of trusted people who have a close relationship with Tails but different interests and different access to information about us. You are part of one of these groups.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="7fadaae9f6cc259e">
        <source>Everybody in group B has an *identical* share B.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="e616ae8d0c8089ff">
        <source>Everybody in group C has an *identical* share C.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="b3938c13055fb499">
        <source>Everybody in group D has an *identical* share D.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9276861a93c741e1">
        <source>Three different shares are needed to reassemble the revocation certificate. For example, shares A1, A2, and A3, or shares A1, B, and C.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="1aac1a8cf31d97be" weblate-flags="no-wrap">
        <source>How to store your share</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="1528970214937e21">
        <source>Please keep your share in an encrypted storage and make it as hard as you can for untrusted people to get a copy of it.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="0078a49b390860a3">
        <source>You can rename the file as long as you keep the number in the file name of your share as it is needed to use the share.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="f930eeea5b90215c">
        <source>Feel free to back up the file but we might also request you to delete it at some point and you should be able to know whether you still have a copy of it or not. It is all-right to lose your share as long as you tell us that you have lost it. It is actually worse to still have a copy of the share "somewhere" while thinking that you don't, than to lose it by mistake.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="f743ccdce5fdf58f">
        <source>Don't hesitate to ask us if you need clarification on the technical aspects of this.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="892793ea759cb088" weblate-flags="no-wrap">
        <source>When to use your share</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a1ca96bc9b238d20">
        <source>Everybody in possession of a share is subscribed to a mailing list.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="9e780087942f82ef">
        <source>If someone in possession of a share gets to learn about a very bad event that happened to many of us and really thinks that we are not capable of revoking the Tails signing key ourselves anymore, then this person should write to the mailing list explaining why she thinks that the signing key needs to be revoked.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="53a779e6fedde6ed">
        <source>Yes, there is no mathematically proven algorithm for this and here is where your judgment as a human being is needed. The description of the very bad event should be checked or backed by enough people to be plausible.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="767da3c7afdd66de">
        <source>People on the list who are also convinced that the signing key should be revoked share their shares until they have 3 different shares. Then they can assemble the revocation certificate and publish it to revoke the signing key.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="7486d1361db84d73">
        <source>Keep in mind that we could still revoke the signing key ourselves as long as three of us are able to communicate and gather their shares. So we only need your help if no more than two of us are still able to communicate.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="c17e285bd53c91a4">
        <source>Unless you really want to start the key revocation process, do not write to this mailing list.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="3f627e2a6a457b83" weblate-flags="no-wrap">
        <source>Further communications</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6b60ad2357252513">
        <source>In case we need to communicate with you about this revocation mechanism in the future, we will always do it through the tails@boum.org mailing list. We might do so for example to:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="8343c320a0cccb0f">
        <source>Ask you to send your share to a new member of your group.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="2813520b44c72342">
        <source>Ask you to delete your share. This could be needed to cancel the power of others people's share: as long as enough of you delete their shares, the few people that might not delete them would end up with unusable shares.</source>
        <target></target>
        <note from="developer">type: Bullet: '  - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="39795598f7304343">
        <source>The tails@boum.org mailing list has its own OpenPGP key, which is signed by the Tails signing key itself:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="40c8b4457c527b5c" weblate-flags="no-wrap">
        <source>    https://tails.net/tails-email.key
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="8b0ebbbeda7401f2">
        <source>So, can we count on you for this?</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="58405a94b6c21f82">
        <source>If you answer positively, we will send you your share and subscribe you to the mailing list.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="c71d6c06b414b815" weblate-flags="no-wrap">
        <source>Thanks, and may the force be with you!
&lt;/pre&gt;
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="42cf8e09b275b331" weblate-flags="no-wrap">
        <source>Keeping the members of the groups B, C, and D up-to-date</source>
        <target></target>
        <note from="developer">type: Title =</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="2a83a16a55856291">
        <source>At least every 2 years, we make sure that the mechanism still works:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="090e1b428e661674">
        <source>We review internally the list of members of each group and decide possible additions to, and removals from, each group.</source>
        <target></target>
        <note from="developer">type: Bullet: '1. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6ac923f76b6c590d">
        <source>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.</source>
        <target></target>
        <note from="developer">type: Bullet: '1. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="75239fa207e2243c">
        <source>We log in to the administration interface of the mailing list, make sure that it still exists, and is configured correctly.</source>
        <target></target>
        <note from="developer">type: Bullet: '1. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="d296ed56b93ab62d" weblate-flags="no-wrap">
        <source><a id="update"/>
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="3e6f446b70555024" weblate-flags="no-wrap">
        <source>Update email</source>
        <target></target>
        <note from="developer">type: Title -</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="0849ed7ca777b49e">
        <source>We send these emails through tails@boum.org to avoid the need for a personal trust relationship between the person sending the mail and the recipient. We don't send shares from groups B, C, or D with tails@boum.org by doing so.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="69765d7a9ff29025" weblate-flags="no-wrap">
        <source>&lt;pre&gt;
Subject: update
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="99583d9df570e7f5">
        <source>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.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="b77b22857d6aff6b">
        <source>Today, we are asking you to:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="0fb962dc95ce1a5e">
        <source>Verify the authenticity of this email, either by verifying that it is signed by the tails@boum.org mailing or by talking directly to someone from the Board.</source>
        <target></target>
        <note from="developer">type: Bullet: '1. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6637fa161a10d1ae" weblate-flags="no-wrap">
        <source>   The tails@boum.org mailing list has its own OpenPGP key, which is
   signed by the Tails signing key itself:
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="b87bdb5c4b1cfaae" weblate-flags="no-wrap">
        <source>   https://tails.net/tails-email.key
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="04cdd284822e6e65">
        <source>Confirm whether you still have in your possession:</source>
        <target></target>
        <note from="developer">type: Bullet: '2. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="258dcccf4f38eeb2">
        <source>Your share of the revocation certificate.</source>
        <target></target>
        <note from="developer">type: Bullet: '   - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="dd696ba5c6d35cef">
        <source>The number NNN in the file name of your share.</source>
        <target></target>
        <note from="developer">type: Bullet: '   - '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="61614dab13d83c53" weblate-flags="no-wrap">
        <source>     The file was named tails-signing-key-revocation-cert.asc.NNN, where
     NNN is a 3 digit number.
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="6f2a3303b0ba4566">
        <source>For the record, the address of the mailing list that you should write to in case you want to assemble the revocation certificate is:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a395e75f35c4987c" weblate-flags="no-wrap">
        <source>    address@example.org
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="8d4626ac00b6508c">
        <source>Do not write to this mailing list unless you really want to start the key revocation process.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="79dd7b205b1f9f73">
        <source>We are also copying below a summary of the mechanism.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="2363b36598e5569b" weblate-flags="no-wrap">
        <source>XXX: Copy the invitation email:
XXX: - Include "You can read a complete description of the distribution mechanism on:"
XXX: - Stop before "So, can we count on you for this?"
&lt;/pre&gt;
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="aa553f852f74ddae" weblate-flags="no-wrap">
        <source>Adding a new member</source>
        <target></target>
        <note from="developer">type: Title -</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="0e3a1f76ae098ca9">
        <source>Send the [[invitation email|signing_key_revocation#invitation]] to the new member.</source>
        <target></target>
        <note from="developer">type: Bullet: '1. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="71c738fdc7d91665">
        <source>If they agree, ask someone else from the same group to send them their share of the key.</source>
        <target></target>
        <note from="developer">type: Bullet: '1. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a725fb74863d3005" weblate-flags="no-wrap">
        <source>   Unfortunately, this reveals some membership information to these two
   people.
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="424eed3a50b01740">
        <source>Ask the new member to confirm the reception of their share.</source>
        <target></target>
        <note from="developer">type: Bullet: '1. '</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="00f9f2b5830140e0" weblate-flags="no-wrap">
        <source><a id="sharing"/>
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="3b4e3af86b368f72" weblate-flags="no-wrap">
        <source>Sharing email</source>
        <target></target>
        <note from="developer">type: Title ###</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="afa09bae6b101af1" weblate-flags="no-wrap">
        <source>&lt;pre&gt;
Subject: sharing
</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="149aecdf8204cd13">
        <source>We asked someone else from your group to send you a copy of your share.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="a7e5ad0681989035">
        <source>Please tell us once you receive it.</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
      <trans-unit xml:space="preserve" id="5af5b390050d5444">
        <source>The address of the mailing list that you should write to in case you want to assemble the revocation certificate is:</source>
        <target></target>
        <note from="developer">type: Plain text</note>
      </trans-unit>
    </body>
  </file>
</xliff>
