Tails/wiki/src/doc/about/openpgp_keys/signing_key_revocation.*.po — Spanish @ Tails translation platform: How to store your share

Translation

Source change

English type: Title =

Spanish

Needs editing

Insufficient privileges for saving translations.

Skip

	English	Spanish	Actions
	Note: In all this document, 'us' refers to the Board.
	You can read a complete description of the distribution mechanism on:	Puedes leer una descripción completa del mecanismo de distribución en:
	https://tails.net/doc/about/openpgp_keys/signing_key_revocation.	https://tails.net/doc/about/openpgp_keys/signing_key_revocation/index.es.html.
	The recipe is public and the only secret component is the list of people who are in possession of the cryptographic material.	La receta es pública y el único componente secreto es la lista de gente que tiene el material criptográfico.
	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.	Te proponemos esto a tí porque confiamos tanto en tus habilidades técnicas para guardar tu porción en un lugar seguro y manipularla como es requerido, sino también porque confiamos en tí como persona que puede tomar una decisión sensata de cuándo usar tu porción y actuar sólo en el interés de Tails.
	The bad things that could happen if the mechanism fails are:	Las cosas malas que podrían pasar si el mecanismo falla son:
	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.	A. La clave de firmado no se revocan cuando deberían. Esto podría permitir a posibles atacantes distribuir imágenes ISO maliciosas de Tails o publicar información maliciosa en nuestro nombre.
	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.	B. La clave de firmado es revocada cuando no debería revocarse. Esto prevendría que la gente pueda verificar nuestras imágenes ISO con OpenPGP hasta que publiquemos una nueva clave de firma.
	Distribution of the shares	Distribución de las porciones
	Each person from the Board, group A, has a different share, A1, A2, ..., An.	Cada persona de tails@boum.org, el grupo A, tiene una porción distinta, A1, A2, ..., An.
	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.
	Everybody in group B has an identical share B.	Todas las personas en el grupo B tienen la misma porción B.
	Everybody in group C has an identical share C.	Todas las personas en el grupo C tienen la misma porción C.
	Everybody in group D has an identical share D.	Todas las personas en el grupo D tienen la misma porción D.
	Three different shares are needed to reassemble the revocation certificate. For example, shares A1, A2, and A3, or shares A1, B, and C.
	How to store your share	Cuándo usar tu porción
	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.
	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.
	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.
	Don't hesitate to ask us if you need clarification on the technical aspects of this.
	When to use your share	Cuándo usar tu porción
	Everybody in possession of a share is subscribed to a mailing list.
	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.
	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.
	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.
	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.
	Unless you really want to start the key revocation process, do not write to this mailing list.
	Further communications	Siguientes comunicaciones
	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:
	Ask you to send your share to a new member of your group.
	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.

Loading…

No matching activity found.

Browse all string changes

Things to check

Trailing newline

Source and translation do not both end with a newline

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

Source string description

type: Title =

Flags

no-wrap

String age

3 years ago

Last updated

4 months ago

Source string age

3 years ago

Translation file

wiki/src/doc/about/openpgp_keys/signing_key_revocation.es.po, string 71