1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
==================================
gemato -- Gentoo Manifest Tool
==================================
:Author: Michał Górny
:License: 2-clause BSD license
Introduction
============
gemato provides a reference implementation of the full-tree Manifest
checks as specified in GLEP 74 [#GLEP74]_. Originally focused
on verifying the integrity and authenticity of the Gentoo ebuild
repository, the tool can be used as a generic checksumming tool
for any directory trees.
Usage
=====
Verification
------------
The basic purpose of gemato is to verify a directory tree against
Manifest files. In order to do that, run the ``gemato verify`` tool
against the requested directory::
gemato verify /var/db/repos/gentoo
The tool will automatically locate the top-level Manifest (if any)
and check the specified directory recursively. If a subdirectory
of the Manifest tree is specified, only the specified leaf is checked.
Creating new Manifest tree
--------------------------
Creating a new Manifest tree can be accomplished using the ``gemato
create`` command against the top directory of the new Manifest tree::
gemato create -p ebuild /var/db/repos/gentoo
Note that for the ``create`` command you always need to specify either
a profile (via ``-p``) or at least a hash set (via ``-H``).
Updating existing Manifests
---------------------------
The ``gemato update`` command is provided to update an existing Manifest
tree::
gemato update -p ebuild /var/db/repos/gentoo
Alike ``create``, ``update`` also requires specifying a profile (``-p``)
or a hash set (``-H``). The command locates the appropriate top-level
Manifest and updates the specified directory recursively.
If a subdirectory of the Manifest tree is specified, the entries
for the specified leaf and respective Manifest files are updated.
Requirements
============
gemato is written in Python and compatible with implementations
of Python 2.7 and Python 3.4+. However, the support for Python 2
is considered 'best effort' and has some known limitations. For example,
non-ASCII paths on command-line do not work.
gemato is currently tested against CPython 2.7, CPython 3.4 through 3.6,
PyPy and PyPy3.
gemato depends only on standard Python library modules and their
backports. The exact runtime dependencies depend on the standard library
version used. Those are:
Python 3.6+
none -- only standard modules are used
Python 3.4, 3.5
- pyblake2 -- for BLAKE2 family of hashes [#pyblake2]_
- pysha3 -- for SHA3 (Keccak) family of hashes [#pysha3]_
Python 2.7
the above, plus:
- bz2file -- for BZip2 compression support [#bz2file]_ [#bz2py2]_
- backports.lzma -- for LZMA/XZ compressed file support [#lzma]_
Additionally, gemato calls the GnuPG executable to work with OpenPGP
signatures. Both GnuPG 1.4.21 and 2.2+ are tested.
References and footnotes
========================
.. [#GLEP74] GLEP 74: Full-tree verification using Manifest files
(https://www.gentoo.org/glep/glep-0074.html)
.. [#pyblake2] BLAKE2 hash function extension module
(https://pypi.python.org/pypi/pyblake2)
(https://github.com/dchest/pyblake2)
.. [#pysha3] SHA-3 (Keccak) for Python 2.7 - 3.5
(https://pypi.python.org/pypi/pysha3)
(https://github.com/tiran/pysha3)
.. [#bz2file] Read and write bzip2-compressed files
(https://pypi.python.org/pypi/bz2file)
(https://github.com/nvawda/bz2file)
.. [#bz2py2] Strictly speaking, Python 2.7 has a ``bz2`` module.
However, this old module version does not support working on open
files nor multiple streams inside a single file. For this reason,
the external module is unconditionally required.
.. [#lzma] Backport of Python 3.3's 'lzma' module for XZ/LZMA compressed
files
(https://pypi.python.org/pypi/backports.lzma)
(https://github.com/peterjc/backports.lzma)
|
