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 requiredb. But also because we trust inyou as a human being to make informed judgment on when to use your share and act only in the interest of Tails.
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.
65
A. The signing key is not revoked whilen it should be. This could allow possible attackers to distribute malicious Tails ISOimages or publish malicious information on our name.
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.
66
B. The signing key is revoked when it should not have been. This would prevent people from verifying our ISOimages with OpenPGP until we publish a new signing key and build trust in it.
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.
68
Each person from tails@boum.orghe Board, group A, has a *different* share, A1, A2, ..., An.
We want to propose youSome 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.
Some years ago, you agreed to be part of a distributed mechanism for the revocation certificate of the Tailssigning key and we sent you a cryptographic share of this revocation certificate.
120
RequestIf they agree, ask someone else from thate same group to send them their share tof the new person in the groupkey.