Recent commits to derivepassphrase.git (5022fff219bf1bc30988d3070e564ad058f0d5c4)

Add Changelog entry for the vault exporter

2024-08-31T22:09:41+02:00

</pre>

Rename vault v0.2/v0.3 classes, and fix API weirdnesses and test coverage

2024-08-31T21:26:49+02:00

The `Reader` classes are now named `VaultNativeConfigParser`, because
`Reader` is a very non-descript name.  The interface is now somewhat more
pythonic, and uses fewer internal branches.  Further tests of the
internals have been added, so the module has 100% test coverage.
</pre>

Add more tests of the storeroom format exporter's internals

2024-08-31T21:24:29+02:00

Further tests are necessary to achieve 100% coverage, but these concern
the detection of format errors, so the test files are rather hard to
generate.
</pre>

Test exporter data loading functionality more robustly

2024-08-31T21:04:32+02:00

Move the `_load_data` function, which deals with determining the correct
vault storage format (with automatic rollover) into the top level, where
the function can be tested in isolation, and stubbed out if necessary.

Also, use the environments with disabled cryptography support to test
for correct failure behavior of the exporter.  Use
`importlib.util.find_spec` instead of an `import` statement to check for
importability of a module, which does not require handling of
`ModuleNotFoundError` if restricted to top-level modules/packages.
</pre>

Move exporter command-line interface into a separate module

2024-08-31T13:32:33+02:00

Also replicate this module structure in the tests, which allows us to
use `pytest.importorskip` to deal with missing `cryptography` support.
</pre>

Add preliminary tests for the exporter

2024-08-25T23:50:03+02:00

Includes basic testing of command-line functionality, explicit examples
of each supported format, and proper hatch environment and dependency
selection (with exporter support, or without) to run tests in.  The
major missing pieces are weird-to-reach error conditions in the
internals of the exporter functions (which require invasive mocking) and
explicit API testing of the exporter functions (i.e. beyond each
exporter's "main" function).  Because the internal API is not yet
stable, particularly the v0.2 and v0.3 exporters, this is currently left
as a TODO.

Since we are attempting to support installations without the
cryptography module, we must ensure the exporter modules all stay
importable without triggering import errors.  (This is also relevant for
pytest's test collection phase, where those modules too are scanned for
doctests.)  Currently we stub out each (sub-)module of the cryptography
package implicitly, such that calling any method on the stub raises an
import error, as well as explicitly through a `STUBBED` attribute on the
exporter module.
</pre>

Add command-line interface to the exporter

2024-08-25T23:31:24+02:00

A new script `derivepassphrase_export` implements a command-line
interface to the exporter machinery.  It is implemented as a separate
script because it has a very different call signature which doesn't
easily map to `derivepassphrase`'s command-line interface.
</pre>

Move vault key and path detection logic into the exporter module

2024-08-18T09:41:16+02:00

Instead of having both exporters reimplement the logic for determining
the vault key and vault configuration path, implement this functionality
in the `derivepassphrase.exporter` package, which is otherwise still
empty.
</pre>

Add prototype for "vault v0.2/v0.3"-type data export

2024-08-18T00:45:19+02:00

Based on a rather direct translation of vault's "legacy" configuration
migrator, for storeroom-enabled builds of vault.
</pre>

Support exports from outside the current directory

2024-08-18T00:14:59+02:00

In the storeroom exporter, pass the storeroom directory explicitly, and
open and glob all bucket files relative to this directory.
</pre>