mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-01-03 05:35:58 +00:00
Code Issues Releases Wiki Activity

docs: fix way too small figures in pdf

Browse source
This commit is contained in:
Marian Beermann 2017-06-05 01:00:41 +02:00
parent 71495b90e0
commit e80c0f7c5e
3 changed files with 10 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
docs/conf.py
View file

@ -207,6 +207,7 @@
latex_elements = { latex_elements = {
'papersize': 'a4paper', 'papersize': 'a4paper',
'pointsize': '10pt', 'pointsize': '10pt',
'figure_align': 'H',
} }
# For "manual" documents, if this is true, then toplevel headings are parts, # For "manual" documents, if this is true, then toplevel headings are parts,

2
docs/internals.rst
View file

@ -27,6 +27,8 @@ chunk is checked against the :ref:`chunks cache <cache>`, which is a
hash-table of all chunks that already exist. hash-table of all chunks that already exist.
.. figure:: internals/structure.png .. figure:: internals/structure.png
:figwidth: 100%
:width: 100%
Layers in Borg. On the very top commands are implemented, using Layers in Borg. On the very top commands are implemented, using
a data access layer provided by the Archive and Item classes. a data access layer provided by the Archive and Item classes.

9
docs/internals/data-structures.rst
View file

@ -204,8 +204,9 @@ commit is written to the new segment. Then, the old segment is deleted
A simplified example (excluding conditional compaction and with simpler A simplified example (excluding conditional compaction and with simpler
commit logic) showing the principal operation of compaction: commit logic) showing the principal operation of compaction:
.. figure:: .. figure:: compaction.png
compaction.png :figwidth: 100%
:width: 100%
(The actual algorithm is more complex to avoid various consistency issues, refer to (The actual algorithm is more complex to avoid various consistency issues, refer to
the ``borg.repository`` module for more comments and documentation on these issues.) the ``borg.repository`` module for more comments and documentation on these issues.)
@ -288,6 +289,8 @@ by their chunk ID, which is cryptographically derived from their contents.
More on how this helps security in :ref:`security_structural_auth`. More on how this helps security in :ref:`security_structural_auth`.
.. figure:: object-graph.png .. figure:: object-graph.png
:figwidth: 100%
:width: 100%
.. _manifest: .. _manifest:
@ -640,6 +643,8 @@ and both are stored in the chunk. Encryption and MAC use two different keys.
Each chunk consists of ``TYPE(1)`` + ``MAC(32)`` + ``NONCE(8)`` + ``CIPHERTEXT``: Each chunk consists of ``TYPE(1)`` + ``MAC(32)`` + ``NONCE(8)`` + ``CIPHERTEXT``:
.. figure:: encryption.png .. figure:: encryption.png
:figwidth: 100%
:width: 100%
In AES-CTR mode you can think of the IV as the start value for the counter. In AES-CTR mode you can think of the IV as the start value for the counter.
The counter itself is incremented by one after each 16 byte block. The counter itself is incremented by one after each 16 byte block.