KurlesHS/restic
1
0
Fork 0
forked from TrueCloudLab/restic
Code Pull requests Activity

Prefer https:// links in the documentation

Browse source 
All the changed urls are available by way of https://. Most of them
already redirect.
This commit is contained in:
Andreas Olsson 2018-12-29 15:55:25 +01:00
parent 0dd805421e
commit 3b68acf853
No known key found for this signature in database
GPG key ID: 210FE3E069ED67A8
5 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/020_installation.rst
View file

@ -72,7 +72,7 @@ macOS
===== =====
If you are using macOS, you can install restic using the If you are using macOS, you can install restic using the
`homebrew <http://brew.sh/>`__ package manager: `homebrew <https://brew.sh/>`__ package manager:
.. code-block:: console .. code-block:: console

6
doc/090_participating.rst
View file

@ -85,7 +85,7 @@ back end is contained in `Design <https://restic.readthedocs.io/en/latest/design
If you'd like to start contributing to restic, but don't know exactly If you'd like to start contributing to restic, but don't know exactly
what do to, have a look at this great article by Dave Cheney: what do to, have a look at this great article by Dave Cheney:
`Suggestions for contributing to an Open Source `Suggestions for contributing to an Open Source
project <http://dave.cheney.net/2016/03/12/suggestions-for-contributing-to-an-open-source-project>`__ project <https://dave.cheney.net/2016/03/12/suggestions-for-contributing-to-an-open-source-project>`__
A few issues have been tagged with the label ``help wanted``, you can A few issues have been tagged with the label ``help wanted``, you can
start looking at those: start looking at those:
https://github.com/restic/restic/labels/help%20wanted https://github.com/restic/restic/labels/help%20wanted
@ -113,7 +113,7 @@ Compatibility
Backward compatibility for backups is important so that our users are Backward compatibility for backups is important so that our users are
always able to restore saved data. Therefore restic follows `Semantic always able to restore saved data. Therefore restic follows `Semantic
Versioning <http://semver.org>`__ to clearly define which versions are Versioning <https://semver.org>`__ to clearly define which versions are
compatible. The repository and data structures contained therein are compatible. The repository and data structures contained therein are
considered the "Public API" in the sense of Semantic Versioning. This considered the "Public API" in the sense of Semantic Versioning. This
goes for all released versions of restic, this may not be the case for goes for all released versions of restic, this may not be the case for
@ -128,7 +128,7 @@ prior versions.
Building documentation Building documentation
********************** **********************
The restic documentation is built with `Sphinx <http://sphinx-doc.org>`__, The restic documentation is built with `Sphinx <https://www.sphinx-doc.org>`__,
therefore building it locally requires a recent Python version and requirements listed in ``doc/requirements.txt``. therefore building it locally requires a recent Python version and requirements listed in ``doc/requirements.txt``.
This example will guide you through the process using `virtualenv <https://virtualenv.pypa.io>`__: This example will guide you through the process using `virtualenv <https://virtualenv.pypa.io>`__:

2
doc/cache.rst
View file

@ -9,7 +9,7 @@ Versions
======== ========
The cache directory is selected according to the `XDG base dir specification The cache directory is selected according to the `XDG base dir specification
<http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html>`__. <https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html>`__.
Each repository has its own cache sub-directory, consisting of the repository ID Each repository has its own cache sub-directory, consisting of the repository ID
which is chosen at ``init``. All cache directories for different repos are which is chosen at ``init``. All cache directories for different repos are
independent of each other. independent of each other.

2
doc/design.rst
View file

@ -276,7 +276,7 @@ the IV for counter mode and the nonce for Poly1305. This operation needs
three keys: A 32 byte for AES-256 for encryption, a 16 byte AES key and three keys: A 32 byte for AES-256 for encryption, a 16 byte AES key and
a 16 byte key for Poly1305. For details see the original paper `The a 16 byte key for Poly1305. For details see the original paper `The
Poly1305-AES message-authentication Poly1305-AES message-authentication
code <http://cr.yp.to/mac/poly1305-20050329.pdf>`__ by Dan Bernstein. code <https://cr.yp.to/mac/poly1305-20050329.pdf>`__ by Dan Bernstein.
The data is then encrypted with AES-256 and afterwards a message The data is then encrypted with AES-256 and afterwards a message
authentication code (MAC) is computed over the ciphertext, everything is authentication code (MAC) is computed over the ciphertext, everything is
then stored as IV \|\| CIPHERTEXT \|\| MAC. then stored as IV \|\| CIPHERTEXT \|\| MAC.

2
doc/manual_rest.rst
View file

@ -181,7 +181,7 @@ locks with the following command:
d369ccc7d126594950bf74f0a348d5d98d9e99f3215082eb69bf02dc9b3e464c d369ccc7d126594950bf74f0a348d5d98d9e99f3215082eb69bf02dc9b3e464c
The ``find`` command searches for a given The ``find`` command searches for a given
`pattern <http://golang.org/pkg/path/filepath/#Match>`__ in the `pattern <https://golang.org/pkg/path/filepath/#Match>`__ in the
repository. repository.
.. code-block:: console .. code-block:: console