Commit 624e507c authored by sajolida's avatar sajolida

Fix broken links

parent 0b8d3f08
......@@ -63,8 +63,8 @@ The cons:
About the removal of Seahorse Nautilus
======================================
As of now, we are explaining how to [[verify ISO images using
`seahorse-nautilus` for GNOME|doc/get/verify_the_iso_image_using_gnome]].
As of now, we are explaining how to verify ISO images using
`seahorse-nautilus` for GNOME.
While reworking the ISO verification scenarios, we pretty much settled on the
idea of removing Seahorse Nautilus as a verification option, at least from the
assistant. Here is why.
......
......@@ -131,6 +131,8 @@ The following steps can be used as an alternative method:
5. Save the document on a USB stick
6. Boot into a system with Internet connection and send your report
<a id="does_not_start"></a>
Tails does not start
--------------------
......
......@@ -8,8 +8,7 @@ volume are saved encrypted and remain available across separate working sessions
<div class="note">
<p>It is only possible to create a persistent volume if the device, USB stick or
SD card, was installed using <span class="application">[[Tails
Installer|doc/first_steps/installation]]</span>.</p>
SD card, was installed using <span class="application">Tails Installer</span>.</p>
<p>This requires a USB stick or SD card of <strong>at least 4 GB</strong>.</p>
......
......@@ -146,7 +146,7 @@ Authenticate the signing key through the OpenPGP Web of Trust
=============================================================
The verification techniques presented until now ([[Firefox extension,
BitTorrent|download/install]], or OpenPGP verification) all rely on some
BitTorrent|install/download]], or OpenPGP verification) all rely on some
information being securely downloaded using HTTPS from our website:
- The *checksum* for the Firefox extension
......
......@@ -3,4 +3,4 @@ cryptographic checksum in the Torrent file.</p>
<p class="openpgp">If you are knowledgeable about OpenPGP, you can do
additional verification using the OpenPGP signature included in the
Torrent file. [[Learn how to do this.|doc/get/verify]]</p>
Torrent file. [[Learn how to do this.|install/download/openpgp]]</p>
......@@ -233,7 +233,7 @@ two techniques to do this verification automatically.</p>
<span class="dvd">[[Burn Tails on a DVD|install/dvd#next]].</span>
<span class="vm">read our [[Introduction to virtual machines|install/vm#next]].</span>
</p>
<p class="openpgp">If you are knowledgeable about OpenPGP, you can do additional verification using the <a href='[[!inline pages="inc/stable_i386_iso_sig_url" raw="yes"]]'>OpenPGP signature</a>. [[Learn how to do this.|doc/get/verify]]</p>
<p class="openpgp">If you are knowledgeable about OpenPGP, you can do additional verification using the <a href='[[!inline pages="inc/stable_i386_iso_sig_url" raw="yes"]]'>OpenPGP signature</a>. [[Learn how to do this.|install/download/openpgp]]</p>
</div>
<a href="" id="download-again" class="">Download again</a>
</div>
......
......@@ -42,7 +42,7 @@ it](https://blog.torproject.org/blog/diginotar-debacle-and-what-you-should-do-ab
It is clear for us that getting an commercial SSL certificate is not enough to
strongly authenticate our website, and for example authenticity of our releases.
That's why we always propose you [[stronger ways of authenticating our Tails
release|doc/get/verify]] using OpenPGP signatures.
release|install/download/openpgp]] using OpenPGP signatures.
Why get a commercial certificate then?
======================================
......
......@@ -36,7 +36,7 @@ Tails developers are not that skilled in documentation writing, so
[[help is needed and much welcome|contribute/how/documentation]]!
Our public email address was renamed to <tails@boum.org>; its [[OpenPGP key|doc/about/openpgp_keys]] was
updated accordingly. We also have [[documented|doc/get/trusting_tails_signing_key]]
updated accordingly. We also have documented
how to get to trust our OpenPGP keys.
GSoC
......
......@@ -81,12 +81,10 @@ Documentation and Website
- The content of the /bugs section of the website was moved to /todo.
- A [[bug concerning MD5 Reborned
Hasher|/doc/get/verify_the_iso_image_using_other_operating_systems]]
Hasher has been documented.
- A bug concerning *MD5 Reborned Hasher* has been documented.
- The instructions for [[manual installation on
Mac|/doc/first_steps/installation/manual/mac]] have been brought
- The instructions for manual installation on
Mac have been brought
back online and the instructions for Linux and Windows have been
improved.
......
......@@ -94,8 +94,8 @@ Documentation and website
- A branch to [[!tails_gitweb_branch feature/cleanup-ikiwiki-setup
"clean up our ikiwiki configuration"]] was started.
- The [[Mac installation
instructions|doc/first_steps/installation/manual/mac]] were made
- The Mac installation
instructions were made
a bit safer.
- The links to files and branches in cgit were fixed.
- The tails-support mailing list is now mentioned on [[Help other
......
......@@ -11,7 +11,7 @@ Documentation and website
* We wrote a small documentation about [[*Claws Mail*|doc/anonymous_internet/claws_mail]].
* We corrected [[some|doc/first_steps/installation/manual/mac]] [[details|doc/first_steps/installation/manual/linux]] in the manual installation documentations, the [[verification documentation|doc/get/verify]], and [[related FAQ questions|support/faq#unetbootin_etc]].
* We corrected some details in the manual installation documentations, the verification documentation, and [[related FAQ questions|support/faq#unetbootin_etc]].
* We added a [[FAQ entry about why we ship the GNOME Desktop|support/faq#gnome]].
......
......@@ -33,7 +33,7 @@ Documentation and website
* We documented [[the languages in which user support is available|support]].
* We reorganized information between the [[Start Tails|doc/first_steps/start_tails]] and the [[Tails does not start|doc/first_steps/bug_reporting/tails_does_not_start]] pages.
* We reorganized information between the [[Start Tails|doc/first_steps/start_tails]] and the Tails does not start pages.
* We published an (incomplete) list of [[organizations doing Tails training|support/learn]].
......
......@@ -75,8 +75,8 @@ Documentation and website
addresses|about/contact]], their scope and policy.
* We improved the instructions for [[resetting a USB
stick|doc/first_steps/reset/mac]] and [[verifying the ISO
image|doc/get/verify_the_iso_image_using_other_operating_systems#mac]] in Mac OS X.
stick|doc/first_steps/reset/mac]] and verifying the ISO
image in Mac OS X.
* We explained [[how to restart GNOME
Shell|support/known_issues#restart-shell]]. This is particularly
......
......@@ -269,5 +269,5 @@ msgid ""
"trusting_tails_signing_key#debian]] using any of those three keys."
msgstr ""
"بنابراین می‌توانید از شگرد آمده در مستندات ما برای [[تأیید دوبارهٔ کلید امضای "
"تیلز با دسته‌کلید دبیان|doc/get/trusting_tails_signing_key#debian]] با هر "
"تیلز با دسته‌کلید دبیان|install/expert/usb#verify-key]] با هر "
"کدام از این سه کلید استفاده کنید."
......@@ -279,6 +279,6 @@ msgid ""
"trusting_tails_signing_key#debian]] using any of those three keys."
msgstr ""
"Vous pouvez donc utiliser la technique décrite dans notre documentation pour "
"[[vérifier davantage la clé de signature Tails avec le trousseau Debian|doc/"
"get/trusting_tails_signing_key#debian]] en utilisant n'importe laquelle de "
"[[vérifier davantage la clé de signature Tails avec le trousseau Debian|install/"
"expert/usb#verify-key]] en utilisant n'importe laquelle de "
"ces trois clés."
......@@ -99,5 +99,5 @@ developers, namely:
So you can use the technique described in our documentation to further
[[verify the Tails signing key against the Debian
keyring|doc/get/trusting_tails_signing_key#debian]] using any of those
keyring|install/expert/usb#verify-key]] using any of those
three keys.
......@@ -29,7 +29,7 @@ is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -31,7 +31,7 @@ is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -32,7 +32,7 @@ you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -31,7 +31,7 @@ version 0.15 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -31,7 +31,7 @@ version 0.16 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -31,7 +31,7 @@ version 0.17 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -31,7 +31,7 @@ upcoming version 0.17.2 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -31,7 +31,7 @@ upcoming version 0.18 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -31,7 +31,7 @@ upcoming version 0.19 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -32,7 +32,7 @@ upcoming version 0.20 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -33,7 +33,7 @@ upcoming version 0.21 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -33,7 +33,7 @@ upcoming version 0.22 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -22,7 +22,7 @@ How to test Tails 0.22.1~rc1?
<a class="download-signature"
href="https://tails.boum.org/torrents/files/tails-i386-0.22.1~rc1.iso.sig">Tails 0.22.1~rc1 signature</a>
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues
of this release</a> and the list of [[longstanding known
......
......@@ -33,7 +33,7 @@ upcoming version 0.23 is out. Please test it and see if all works for you.</p>
</li>
<li>
<p>
[[Verify the ISO image|doc/get/verify]].
Verify the ISO image.
</p>
</li>
<li>
......
......@@ -22,7 +22,7 @@ How to test Tails 1.0~rc1?
<a class="download-signature"
href="https://tails.boum.org/torrents/files/tails-i386-1.0~rc1.iso.sig">Tails 1.0~rc1 signature</a>
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of [[longstanding known
issues|support/known_issues]].
......
......@@ -23,7 +23,7 @@ How to test Tails 1.1~beta1?
Note that there is no automatic upgrade targetting this release!
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -23,7 +23,7 @@ How to test Tails 1.1~rc1?
Note that there is no automatic upgrade targetting this release!
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -22,7 +22,7 @@ How to test Tails 1.2~rc1?
<a class="download-signature"
href="https://tails.boum.org/torrents/files/tails-i386-1.2~rc1.iso.sig">Tails 1.2~rc1 signature</a>
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -22,7 +22,7 @@ How to test Tails 1.3~rc1?
<a class="download-signature"
href="https://tails.boum.org/torrents/files/tails-i386-1.3~rc1.iso.sig">Tails 1.3~rc1 signature</a>
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -22,7 +22,7 @@ How to test Tails 1.4~rc1?
<a class="download-signature"
href="https://tails.boum.org/torrents/files/tails-i386-1.4~rc1.iso.sig">Tails 1.4~rc1 signature</a>
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -29,7 +29,7 @@ more information.
<a class="download-signature"
href="https://tails.boum.org/torrents/files/tails-i386-1.5~rc1.iso.sig">Tails 1.5~rc1 signature</a>
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -22,7 +22,7 @@ How to test Tails 1.7~rc1?
<a class="download-signature"
href="https://tails.boum.org/torrents/files/tails-i386-1.7~rc1.iso.sig">Tails 1.7~rc1 signature</a>
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -54,7 +54,7 @@ to port it to GNOME Shell (issued in January, 2015) was unsuccessful.
Note that there is no automatic upgrade applicable to this release.
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -92,7 +92,7 @@ to port it to GNOME Shell (issued in January, 2015) was unsuccessful.
2.0~beta1 even though it is very slow.
Note that there is no automatic upgrade from 1.8.2 to this release.
1. [[Verify the ISO image|doc/get/verify]].
1. Verify the ISO image.
1. Have a look at the list of <a href="#known_issues">known issues of
this release</a> and the list of
......
......@@ -43,7 +43,7 @@ USB stick.
1. Download the latest [test ISO](http://nightly.tails.boum.org/build_Tails_ISO_devel/).
1. Use any officially supported way to
[[install|doc/first_steps/installation]] the experimental ISO image
install the experimental ISO image
to first device, that we will call *Alpha*, that can be a DVD or a USB stick. At this point,
device *Alpha* does not support UEFI.
......@@ -52,9 +52,9 @@ USB stick.
1. Take detailed notes about how this boot goes.
1. *Clone & Install* device *Alpha* onto another USB stick [[with <span
1. *Clone & Install* device *Alpha* onto another USB stick with <span
class="application">Tails
Installer</span>|doc/first_steps/installation]]. We
Installer</span>. We
will call this second device *Beta*, and it supports UEFI.
1. Get the computer you are really interested in using with Tails.
......
......@@ -28,8 +28,8 @@ Notable user-visible changes include:
device. All of the USB drive must be dedicated to Tails; a bit of
extra space is reserved so that future Tails releases will fit when
upgrading, and the rest can be used for persistence (see below) or
manually formatted if the user so wishes. See [[the USB installation
documentation|doc/first_steps/installation]] for details.
manually formatted if the user so wishes. See the USB installation
documentation for details.
* Persistence can optionally be used when running Tails from a USB
drive. Application configurations and arbitrary directories can be
......
......@@ -24,7 +24,7 @@ years ago. Tails 1.0 marks the 36th stable release since then.
We have been working since then on the many features we think
are essential both in terms of security and usability:
- [[USB installer|doc/first_steps/installation]]
- USB installer
- [[automatic upgrades|doc/first_steps/upgrade]]
- [[persistence|doc/first_steps/persistence]]
- [[support for Tor bridges|doc/first_steps/startup_options/bridge_mode]] and
......
......@@ -17,8 +17,8 @@ issues|security/Numerous_security_holes_in_1.3.1]] and all users must
- The **Florence** virtual keyboard can now be used with touchpads
again.
- **Tails Installer** does not list devices that are [[too small to
be supported|doc/first_steps/installation]].
- **Tails Installer** does not list devices that are too small to
be supported.
There are numerous other changes that may not be apparent in the daily
operation of a typical user. Technical details of all the changes
......
......@@ -47,7 +47,7 @@ You can have a look at:
guidelines|doc/first_steps/bug_reporting]].</p>
<p>If Tails does not start, please see our specific
[[reporting guidelines|doc/first_steps/bug_reporting/tails_does_not_start]].</p>
[[reporting guidelines|doc/first_steps/bug_reporting#does_not_start]].</p>
</div> <!-- #bugs -->
......
......@@ -116,7 +116,7 @@ many people would think the website is broken while it is not.
We prefer to provide weak security, using a commercial certificate, that still
works for most people. At the same time, we make clear this security is limited
and encourage stronger ways of verifying the authenticity of Tails once
downloaded. See our documentation on [[verifying the ISO|doc/get/verify]].
downloaded. See our documentation on [[verifying the ISO image using OpenPGP|install/download/openpgp]].
<a id="hardware"></a>
......@@ -661,7 +661,7 @@ liar; the answer of a true liar would always be "no".
- To verify the integrity of a DVD from a separate trusted system, you can
verify the signature of the ISO image as documented in [[verify the ISO image
using the command line|doc/get/verify_the_iso_image_using_the_command_line]]
using OpenPGP|install/download/openpgp]]
against the DVD itself.
- There is no documented method of verifying the integrity of a USB stick or SD
......
......@@ -7,7 +7,7 @@ Problems starting Tails
This section lists known problems with specific hardware. To report a problem
with different hardware see our [[report guidelines when Tails does not
start|doc/first_steps/bug_reporting/tails_does_not_start]].
start|doc/first_steps/bug_reporting#does_not_start]].
<a id="problematic-usb-sticks"></a>
......@@ -178,7 +178,7 @@ These machines do not start on USB sticks created using Tails USB
Installer, due to a firmware limitation.
A workaround for some of these machines is to use the [[manual
installation process|doc/first_steps/installation/manual/linux]].
installation process|install/linux/usb]].
Note, however, that this technique does not allow you to set up
a persistent volume.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment