2. Tails
3. wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

has:suggestion

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location
• Component and priority

	Translation	Source string	Target string
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	[[!meta title="Revocation of the Tails signing key"]]
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Polish	[[!meta title="Revocation of the Tails signing key"]]
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Serbian (Latin script)	[[!meta title="Revocation of the Tails signing key"]]
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Indonesian	[[!meta title="Revocation of the Tails signing key"]]
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	This document proposes a mechanism for the distribution and activation of the revocation certificate of the Tails signing key.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Status
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	This document is obsolete.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	It will be simplified or removed by [[!tails_gitlab tails/summit/-/issues/36]].
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Goals
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Covered by the current proposal:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Catalan	Prevent any single individual from revoking our signing key.	- Evitar que qualsevol persona revoqui la nostra clau de signatura.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Prevent any single individual from revoking our signing key.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Allow a coalition of people from the Board to revoke our signing key in case most of the people from the Board become unavailable.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	People not from the Board shouldn't know how the shares are spread and who has them.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	People in possession of a share of the revocation certificate of the signing key should have instructions on how to use it if needed.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Groups
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	We define four complementary groups of trusted people:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Group A: people from the Board themselves
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Group B
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Group C
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Group D
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	All these people should have an OpenPGP key and understand what a revocation certificate is.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Cryptographic shares
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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`.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	The following combinations of people could get together and reassemble their shares to reconstruct a complete revocation certificate:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Three people from the Board: A{3}
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Two people from the Board and one person not from the Board: A{2}+(B|C|D)
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	One person from the Board, and two people not from the Board but from two different groups: A+(B|C|D){2}
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Three people not from the Board but from three different groups: (B+C+D){3}
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	We generate these shares:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	N shares, one for each person from the Board
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	1 share for people in group B
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	1 share for people in group C
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	1 share for people in group D
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Who knows what
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	People from the Board know the composition of each group
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	People not from the Board:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Are explained in which circumstances they should revoke the signing key
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Are told to write to a certain contact email address if they decide to revoke the signing key
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Are told that they need three different shares to reassemble the revocation certificate
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Infrastructure
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Everybody who owns a share is subscribed to a mailing list.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	This mailing list is hosted on a trusted server different from boum.org to be more resilient than our usual communication channels.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Changing the members of the groups B, C, or D
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	To add someone to a given group:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Request someone from that group to send her share to the new person in the group.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	To remove someone from a given group:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Send new shares to everybody except to the person who is being removed.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Let's hope that this doesn't happen very often :)
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Russian	Let's hope that this doesn't happen very often :)	Надеемся, это не будет происходить слишком часто :)
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Expiry
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Invitation email
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Someone who has a personal trust relationship with the person being invited sends this email.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	<pre> Subject: distribution
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Hi,
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	We want to propose you to be part of a distributed mechanism for the revocation certificate of the Tails signing key.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Note: In all this document, 'us' refers to the Board.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	You can read a complete description of the distribution mechanism on:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	https://tails.net/doc/about/openpgp_keys/signing_key_revocation.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	The recipe is public and the only secret component is the list of people who are in possession of the cryptographic material.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	The bad things that could happen if the mechanism fails are:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Distribution of the shares
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Each person from the Board, group A, has a *different* share, A1, A2, ..., An.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Everybody in group B has an *identical* share B.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Everybody in group C has an *identical* share C.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Everybody in group D has an *identical* share D.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Three different shares are needed to reassemble the revocation certificate. For example, shares A1, A2, and A3, or shares A1, B, and C.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	How to store your share
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Don't hesitate to ask us if you need clarification on the technical aspects of this.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	When to use your share
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Everybody in possession of a share is subscribed to a mailing list.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Unless you really want to start the key revocation process, do not write to this mailing list.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Further communications
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Ask you to send your share to a new member of your group.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	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.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	The tails@boum.org mailing list has its own OpenPGP key, which is signed by the Tails signing key itself:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	So, can we count on you for this?
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	If you answer positively, we will send you your share and subscribe you to the mailing list.
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Thanks, and may the force be with you! </pre>
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	Keeping the members of the groups B, C, and D up-to-date
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	At least every 2 years, we make sure that the mechanism still works:
	Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Portuguese	We review internally the list of members of each group and decide possible additions to, and removals from, each group.

• 1 / 2
  / 2