https://git.schokokeks.org/derivepassphrase.git/tree/fdbea449cda2a00785dd803c43cf9dbec2995ba1 Recent commits to derivepassphrase.git (fdbea449cda2a00785dd803c43cf9dbec2995ba1) 2024-11-26T14:26:21+01:00 tag:gitlist.org,2012:commit/fdbea449cda2a00785dd803c43cf9dbec2995ba1 Let the `running_ssh_agent` test fixture report the agent type 2024-11-26T14:26:21+01:00 Marco Ricci software@the13thletter.info <pre>In the current test scenario, where multiple SSH agents are spawned if possible, it is highly unhelpful to know *that* a running SSH agent failed, but not *which* agent did. For debugging purposes, it is better if the `running_ssh_agent` test fixture reports not only the agent's socket, but also its type. It is sufficient to have the type passed as a fixture output/test function input, because `pytest` will then pretty-print it when a test function fails. &lt;/pre&gt; tag:gitlist.org,2012:commit/8a56dbdafab38d5493e1aee317f9fe7ec480c156 Decouple deterministic signatures from general SSH agent detection 2024-11-26T14:12:53+01:00 Marco Ricci software@the13thletter.info <pre>Instead of tying deterministic signatures directly to the detection of Pageant specifically, add a general mechanism for attempting to infer the connected SSH agent from its reported list of extensions. This moves the question of *how* we detect certain SSH agents out of the deterministic signature checking function. Alas, OpenSSH does not support the extension query message we issue, despite them supporting the extension system in general *and* stewarding the SSH agent protocol specification which defines this message normatively. So our implementation must tolerate a moderate level of spec violation. &lt;/pre&gt; tag:gitlist.org,2012:commit/b5cb2824fdb57c10cc1021ebe284d33426824a28 Fix test suite to actually test deterministic signature support 2024-11-26T14:03:34+01:00 Marco Ricci software@the13thletter.info <pre>So far, the test suite was silently passing for me, because it requires either a patched version or a not-yet-released version of PuTTY to actually run the tests against Pageant (which is the main beneficiary of deterministic signature detection). Actually plugging in a suitable patched Pageant version revealed a couple of key places where we silently assume that the key type alone determines its suitability for `derivepassphrase`. This commit rectifies that. &lt;/pre&gt; tag:gitlist.org,2012:commit/ba14c709ba5136482a88d3964e62755d155baf9f Fix spurious overloaded signature mismatch 2024-11-26T13:23:33+01:00 Marco Ricci software@the13thletter.info <pre>&lt;/pre&gt; tag:gitlist.org,2012:commit/b630c463f6443e090f728d004ef34c8cdf5dc2c6 Indicate external links in non-API documentation as well 2024-11-26T13:21:54+01:00 Marco Ricci software@the13thletter.info <pre>&lt;/pre&gt; tag:gitlist.org,2012:commit/20931ed0c7a376df2fc2a19746a0ed96fe755ace Split the SSH key how-to into how-to and reference documents 2024-11-26T00:32:29+01:00 Marco Ricci software@the13thletter.info <pre>Because the original how-to discussed both prerequisites and the how-to of SSH keys, it was tonally inconsistent. It makes much more sense from a reading flow perspective to move the discussion of prerequisites into a separate reference document and link to it from the how-to page. So do exactly that. Relative to the old how-to page, the new prerequisites reference page additionally includes sections on how to determine the SSH key type from the algorithm name used in the wire protocol, and sample transcripts for generating new SSH keys suitable for `derivepassphrase vault`; this is based on feedback for the old how-to page. The new how-to page also shows the actual key selection dialog instead of only the command-line to run. &lt;/pre&gt; tag:gitlist.org,2012:commit/29b26ee3335a21a4e5ef5760cc8b705456d8f78d Make suitable SSH key listing easier to distinguish 2024-11-26T00:31:20+01:00 Marco Ricci software@the13thletter.info <pre>On the one hand, truncate and align the listing as two columns, not three, by combining key type and (truncated) key data into one column. For heterogenous lists with different key types, this nicely sets off the comment column (which the user can change to help distinguish the keys) from the key data (which the user cannot change). On the other hand, if truncating the key data for the display, truncate the *front* of the data, not the back. For homogenous lists, this generally leads to better distinguishable key listings: the front contains information common to all keys (the wire-encoded key type), but the back contains key-specific information (for RSA, Ed25519 and Ed448 keys at least). &lt;/pre&gt; tag:gitlist.org,2012:commit/0e01382a7480ceaee27696655cc62e380263822c Add changelog entry for deterministic DSA/ECDSA signature support 2024-11-23T19:15:56+01:00 Marco Ricci software@the13thletter.info <pre>Do not mention the new how-to in the changelog, because that is not part of the program history and only pollutes the changelog view. For the same reason, also purge the existing mention of the tutorial in the changelog view. &lt;/pre&gt; tag:gitlist.org,2012:commit/d28e3c32a2df210a095c9820ffb7a3a33d0dbe1a Merge topic branch 'pageant-deterministic-signatures' into topic branch ssh-key-howto 2024-11-23T19:03:23+01:00 Marco Ricci software@the13thletter.info <pre>* t/pageant-deterministic-signatures: Support the "all signatures are deterministic" feature of some SSH agents Support one-off SSH agent client child contexts &lt;/pre&gt; tag:gitlist.org,2012:commit/423a21a6cc542c455a081e1ebab16c8cf5c3a8ad Add how-to for setting up an SSH key for `derivepassphrase vault` 2024-11-23T18:50:10+01:00 Marco Ricci software@the13thletter.info <pre>We explain the necessary software/operating system prerequisites and configurations. We further prominently note that Windows is currently not supported, and that `gpg-agent` behaves differently than other agents in regard to SSH key management. We further clean up the list of future work, and ensure styling consistency with the basic setup (passphrase) tutorial. &lt;/pre&gt;