2. Tails
3. wiki/src/news/signing_key_transition.*.po
4. Spanish
5. Zen

3
	English type: Plain text [[!meta title="Transition to a new OpenPGP signing key"]]
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/580 · 58 Needs editing
5
	English type: Plain text Tails is transitioning to a new OpenPGP signing key.
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/520 · 52 Needs editing
6
	English type: Plain text The signing key is the key that we use to:
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/420 · 42 Needs editing
7
	English type: Bullet: ' - ' Sign our official ISO images.
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/290 · 29 Needs editing
8
	English type: Bullet: ' - ' Certify the other [[OpenPGP keys|doc/about/openpgp_keys]] used by the project.
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/780 · 78 Needs editing
10
	English type: Plain text <p>The previous signing key is safe and, to the best of our knowledge, it has not been compromised.</p>
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/1040 · 104 Needs editing
11
	English type: Plain text <p>We are doing this change to improve our security practices when manipulating such a critical piece of data.</p>
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/1150 · 115 Needs editing
14
	English type: Plain text <ul> <li>The old key can still be used to verify Tails 1.3 ISO images.</li> <li>The new key will be used to sign ISO images starting from Tails 1.3.1.</li> </ul>
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/1660 · 166 Needs editing
15
	English type: Title = Import and verify the new signing key
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/370 · 37 Needs editing
16
	English type: Plain text Click on the following button to download and import the new signing key:
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/730 · 73 Needs editing
17
	English type: Plain text <a class="download-key" href="https://tails.net/tails-signing.key">new Tails signing key</a>
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/930 · 93 Needs editing
18
	English type: Plain text The new signing key is itself signed by the old signing key. So you can transitively trust this new key if you had trusted the old signing key.
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/1430 · 143 Needs editing
19
	English type: Plain text To verify that the new key is correctly signed by the old key, you can execute the following command:
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/1010 · 101 Needs editing
20
	English type: Plain text gpg --check-sigs A490D0F4D311A4153E2BB7CADBB802B258ACD84F
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/620 · 62 Needs editing
21
	English type: Plain text The output should include a signature of the new key by the old key such as:
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/760 · 76 Needs editing
22
	English type: Plain text sig! 0x1202821CBE2CD9C1 2015-01-19 Tails developers (signing key) <tails@boum.org>
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/960 · 96 Needs editing
23
	English type: Plain text In this output, the status of the verification is indicated by a flag directly following the "`sig`" tag. A "`!`" indicates that the signature has been successfully verified.
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/1740 · 174 Needs editing
24
	English type: Title = Security policy for the new signing key
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/390 · 39 Needs editing
25
	English type: Plain text Here is the full description of the new signing key:
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/520 · 52 Needs editing
26
	English type: Plain text <pre> pub 4096R/0xDBB802B258ACD84F 2015-01-18 [expires: 2017-01-11] Key fingerprint = A490 D0F4 D311 A415 3E2B B7CA DBB8 02B2 58AC D84F uid [ unknown] Tails developers (offline long-term identity key) <tails@boum.org> uid [ unknown] Tails developers <tails@boum.org> sub 4096R/0x98FEC6BC752A3DB6 2015-01-18 [expires: 2017-01-11] sub 4096R/0x3C83DCB52F699C56 2015-01-18 [expires: 2017-01-11] </pre>
	Spanish ↹ ↵ NBS … « » “ ” SHY ‐ – — 0/4670 · 467 Needs editing