https://git.schokokeks.org/derivepassphrase.git/tree/28b4fc2f4e5d7e0a0e5f61ea2730a56fa942b7b8Recent commits to derivepassphrase.git (28b4fc2f4e5d7e0a0e5f61ea2730a56fa942b7b8)2024-10-05T13:06:16+02:00tag:gitlist.org,2012:commit/28b4fc2f4e5d7e0a0e5f61ea2730a56fa942b7b8Suggest new reference documentation: vault(1) configuration2024-10-05T13:06:16+02:00Marco Riccisoftware@the13thletter.info
<pre>There is currently no documentation detailing what the vault(1)
configuration should look like. In particular, there is no
documentation on the `derivepassphrase`-specific settings anywhere
(outside the API reference).
</pre>
tag:gitlist.org,2012:commit/f7a310b0c3a7757112ad31583e90b28973024766Add a tutorial: setting up three services with master passphrase2024-10-05T09:04:28+02:00Marco Riccisoftware@the13thletter.info
<pre>The new tutorial is an introductory tutorial that deals with setting up
the first few services with `derivepassphrase vault`. It deals with
installing the software and configuring the first three services. I've
included one out-of-scope item (a one-time-password hardware token) and
one ill-specified requirement on special characters as practical
examples of things a new user might actually encounter in practice, and
how to deal with these (or not).
The tutorial is complete content-wise, but probably needs some
copy-editing, and definitely needs some practical feedback. The
installation section is also untested, and lacking in comprehensiveness,
as there are multiple sane ways to install Python software such as this
one. Once other documentation is complete, this tutorial may also need
some minor revision on whether and where to link to further topics that
were only briefly touched here.
</pre>
tag:gitlist.org,2012:commit/7cd9237f42004c3548aebfe609ba84cff11e4756Add some ideas for missing documentation pages2024-10-04T10:59:28+02:00Marco Riccisoftware@the13thletter.info
<pre>These are likely documentation entries that are anticipated, and yet
uncovered. This includes most of the "hard" stuff: tutorials and
how-tos. (The reference part is easy, and the explanation part only
slightly less so.)
</pre>
tag:gitlist.org,2012:commit/59082d1f81b629c4be67bdcce2977db289d7c3afTell MkDocs to ignore scriv's changelog snippets2024-10-04T10:55:32+02:00Marco Riccisoftware@the13thletter.info
<pre>The master changelog file is included, of course, but we don't want
MkDocs to bother with the single snippets (rendering them, generating
warnings that they're not part of the navigation tree, etc.).
</pre>
tag:gitlist.org,2012:commit/b0d6fe8ee3208a5c123e546aa931ce06306ad8f6Update required Python version in the README2024-10-03T13:40:52+02:00Marco Riccisoftware@the13thletter.info
<pre>This was forgotten while adding Python 3.9 support.
</pre>
tag:gitlist.org,2012:commit/7bd5c68e2b3448a44f2b0faeb3025e9974ed3fb6Relax hypothesis deadline for another slow-ish test2024-10-03T13:30:36+02:00Marco Riccisoftware@the13thletter.info
<pre>The vault settings validation test keeps timing out on my older
hardware, when running without the C tracer and at moderate power saving
settings. I can only presume it would time out similarly on even
lower-powered hardware, such as a Raspberry Pi.
</pre>
tag:gitlist.org,2012:commit/ba27276a76a263a2d866bc55eca012f927c34877Merge topic branch 'issue15-graceful-af_unix-degredation' into master2024-10-02T20:35:24+02:00Marco Riccisoftware@the13thletter.info
<pre>* t/issue15-graceful-af_unix-degredation:
Fail gracefully if UNIX domain socket support is unavailable
GitHub: Closes #15.
</pre>
tag:gitlist.org,2012:commit/27f9bd183d7b124ddf137b536d1063dd64db3c66Fail gracefully if UNIX domain socket support is unavailable2024-10-02T19:26:30+02:00Marco Riccisoftware@the13thletter.info
<pre>To talk to the SSH agent, we currently require UNIX domain socket
support, but not every Python on every system supports this (notably:
Windows). If we detect such missing support, fail gracefully and with
a useful error message, instead of a technical reason such as
`AttributeError`.
Besides the new failure modes that API consumers will need to handle,
this results in one more observable change: socket objects passed to the
`SSHAgentClient` constructor are now required to be already connected.
The constructor will no longer prepare sockets it didn't create itself
in any way.
This new failure behavior also has consequences for the tests, which so
far have naively assumed UNIX semantics and UNIX domain socket support.
So change the testing machinery to automatically skip any test that
involves constructing a custom SSH agent client *and* expecting that
step to go well. Furthermore, since the "no support" constellation can
be reasonably well simulated even on systems that *do* have UNIX domain
socket support (via pytest's monkeypatching fixture), include explicit
tests on the API and the CLI level for the "no support" constellation,
in any case.
</pre>
tag:gitlist.org,2012:commit/2511d75900a3fddc676ede50f9b5310a6dae8b97Merge topic branch 'support-py39' into master2024-10-02T09:32:06+02:00Marco Riccisoftware@the13thletter.info
<pre>* t/support-py39:
Add changelog entry for Python 3.9 support
Add support for Python 3.9
Accomodate known slow tests in hypothesis deadline
Fix awkward parametrization declaration for SSH agent client tests
</pre>
tag:gitlist.org,2012:commit/b815a40b7b829470af7ea98e4065a563e518d963Add changelog entry for Python 3.9 support2024-10-02T09:31:40+02:00Marco Riccisoftware@the13thletter.info
<pre></pre>