Recent commits to derivepassphrase.git (c07bbb7d20a02a1991ae529cb3ecf25dda42bd68)

Raise KeyError when signing key is not loaded into SSH agent

2024-06-30T16:37:52+02:00

</pre>

Distinguish errors when constructing SSH agent client

2024-06-30T16:37:52+02:00

If we cannot connect to the SSH agent, if it is because we cannot
determine its address, then raise a `KeyError`, otherwise pass the
original `OSError` through, instead of blindly converting everything to
`RuntimeError`.
</pre>

Introduce TrailingDataError for trailing data in SSH agent responses

2024-06-30T16:37:52+02:00

</pre>

Distinguish between a key lookup error in the SSH agent and other communication/runtime errors

2024-06-30T16:37:52+02:00

</pre>

Rename SequinExhaustedException to SequinExhaustedError

2024-06-30T16:37:52+02:00

This is Python, not Java.
</pre>

Rename and regroup all test files and test cases

2024-06-30T16:27:37+02:00

Adhere to standard testing best practices: name tests after the module
they test (and move all such tests into the same testing module), group
related tests within a module into classes, and move common testing
functionality and test data into separate modules.  Grouping related
tests into classes also means that tests with common prerequisites (such
as an available SSH agent) can then be skipped in bulk, if necessary.
</pre>

Add finished command-line interface, with tests

2024-06-22T21:19:30+02:00

Add a finished command-line interface, with interface parity with
vault v0.3.  The implementation has 100% coverage, including the
tests... even if the tests still contain a lot of manual code and data
duplication.  The project settings were updated as well, mostly
expanding the scope of what is covered by type checking and what is
(not) covered by coverage testing.
</pre>

Fortify the argument parsing and handling in the command-line interface

2024-06-22T21:19:30+02:00

Currently, we use a one-to-one correspondence between command-line
argument name and function argument, via catch-all keyword arguments.
This is very unwieldy to use with type checking, it exposes us to name
clashes with Python keywords, and it doesn't even save that much typing
effort because the arguments still ought to be documented in the
documentation anyway. Therefore, introduce an explicit target parameter
name for the `click` interface and corresponding explicit function
arguments. (The implicit list of (function) arguments that `click`
passes to the function is already readily available in the context
object.)

As a related problem, the code for checking whether incompatible options
were specified also relies (excessively cleverly) on command-line
argument names and function argument names being equal, and sometimes
conflates short and long option names, leading to it missing some
examples of incompatible options. Therefore, instead, explicitly build
a map of (short and long) option names to option objects and test
whether incompatible option objects were used.
</pre>

Move typing classes into separate module `derivepassphrase.typing`

2024-06-22T21:19:30+02:00

In particular, include type guard functions here as well.
</pre>

Support textual passphrases, if it is safe

2024-06-22T21:19:30+02:00

Some level of awareness is necessary to support passphrases stored in
(JSON) config files.  We reject the passphrase if there are multiple
Unicode representations (and thus UTF-8 representations) of the same
text but with different normalizations.  In such a case, a byte string
must be used, and the value cannot currently be stored in the JSON
config file.
</pre>