Files
DodoSSH/src/DodoSSH.Client.Domain/SshKeySecret.cs
T
jaap-jan e3fd3e1728 Sync and authenticate with SSH keys on the client
Completes the client half of SSH keys: they sync alongside hosts, appear in
their own list, and can be selected to authenticate a connection instead of
typing a password.

The reconciler and the repository were Host-typed throughout, so the choice was
to generalise them or to keep a second copy per item type. Generalised, because
ItemReconciler's whole premise is that the pull and the push paths must answer
the same collision the same way — two copies would drift the first time one of
them was fixed. What is genuinely per-type now arrives through
IItemKind<TSecret>: the cipher, the merge, the plaintext columns, and the noun
to use when telling a person what happened to their item. Generic where the
server's IItemKind is not, and for the reason that reverses there — the client
needs the concrete type, because it merges field by field.

The pull filter is derived from the same registry that builds the reconcilers.
That is the specific failure being designed out: an item type that encrypts,
merges and lists perfectly and is never once requested from the server, so it
works on the machine that made it and exists nowhere else.

No client cache migration. The item table's primary key and the outbox's unique
index already carry the entity type, and AadResourceTypes already mapped SshKey
— so a host and a key may share an id and never see each other's rows, which
SshKeySyncTests now arranges deliberately.

A key hands the server nothing in plaintext. There is a public_key_fingerprint
column and it would be accepted; leaving it null is deliberate. A fingerprint is
not secret but it is a stable identifier for a key pair, so filling it would let
an operator tell which of their users hold the same key and correlate one across
vaults, for a column nothing reads. The design allows itself one plaintext
concession — the relay address, which the relay cannot work without — and this
is not that.

A key is chosen per connection rather than bound to a host, which works the way
ssh -i does. Binding one needs a field on HostSecret and therefore a payload
schema bump, which makes every host written afterwards read-only on an older
build; worth doing deliberately rather than as a side effect of adding keys.

Three things this found, all of them by being falsified rather than by review:

- Making the reconciler generic silently turned a record comparison into
  reference equality, because == on a type parameter is not value equality. The
  effect would have been a conflict recorded on every pass for an unacknowledged
  create that had in fact landed. Sabotaging the fix left all 73 tests passing —
  nothing covered that branch — so ConflictMatrixTests now has
  AnUnacknowledgedCreateThatDidLand_IsDroppedQuietly, which fails without it.

- A test asserting that a blank passphrase reaches SSH.NET as null was vacuous:
  it exercised the editor, not the credential path, and passed with the guard
  deleted. Resolved by making SshKeySecret.Passphrase normalise an empty string
  to null, so there is one spelling of one state — which also keeps two clients
  from producing different payload bytes for an identical key. That exposed a
  wider gap: SshKeySecret, its codec and its merge had no direct unit tests at
  all. They have 25 now.

- The reason first given for that normalisation was false. It claimed SSH.NET
  rejects a passphrase supplied for an unprotected key; measured against a real
  sshd it ignores it and authenticates anyway. Corrected everywhere it was
  stated and recorded in docs/platform-flags.md. The same test file also closes
  a real hole: SshPrivateKeyCredential had never been exercised against a
  server, because the existing key test builds SSH.NET's auth method directly
  and bypasses the path a vault-held key actually takes.

Only one editor may be open at a time. Both sit in the same 340-pixel column as
Auto rows and their heights together exceed it at the window's minimum size, so
two open editors put the lower one's Save and Cancel past the bottom edge — the
same failure this window already shipped once with the setup screens. Expressed
as a state rule because that is the only form of it this repository can check:
nothing here loads a .axaml. The refusal keeps what was typed, since in the key
editor that is a pasted private key the user may have nowhere else.

The end-to-end slice now carries a key as well as a host, so both item types go
through the real API, the real PostgreSQL and the real crypto in one pass — the
three hand-kept mappings between enums that do not line up are the reason that
is worth doing rather than trusting the unit suites.

735 tests green, including the container-backed SSH and end-to-end suites. Zero
warnings, dotnet format clean.
2026-07-29 20:27:23 +02:00

137 lines
6.3 KiB
C#

using System.Diagnostics.CodeAnalysis;
namespace DodoSSH.Client.Domain;
/// <summary>
/// An SSH key pair as the user sees it, decrypted.
/// </summary>
/// <remarks>
/// <para>
/// The private key is the most valuable thing this product stores, and it is held here as an ordinary
/// string, in managed memory, exactly like <see cref="HostSecret.Notes"/> and every passphrase in the
/// client. That is a deliberate choice rather than an oversight, and it is worth being plain about what it
/// does and does not give you.
/// </para>
/// <para>
/// It does not give you a zeroable buffer. A .NET string cannot be wiped, so the key material lives until
/// the garbage collector reuses the memory, and a process dump taken in the meantime contains it. The
/// alternative — libsodium's guarded memory, which <c>DodoSSH.Crypto</c> uses for the vault keys — was
/// considered and rejected here for one reason: the passphrase protecting this key, the password on the next
/// item, and the decoded JSON the codec produced are all strings on the same heap. Protecting one field
/// among them would be a measure that reads as security and buys nothing, and the honest place for that
/// effort is the threat this design actually addresses, which is the server and the disk rather than another
/// process running as the same user. See <c>LocalCacheProtector</c>, which says the same thing about the
/// cache.
/// </para>
/// <para>
/// What it does give you: the key never reaches the disk in plaintext and never reaches the server at all.
/// It is sealed under the vault key before it leaves this type, and SSH.NET is handed it through a
/// <c>MemoryStream</c> rather than a file, so there is no temporary key file to leak or forget.
/// </para>
/// </remarks>
public sealed record SshKeySecret : IVaultSecret
{
private readonly string? passphrase;
/// <summary>What the user calls this key.</summary>
public required string Label { get; init; }
/// <summary>
/// The private key, in the armoured form <c>ssh-keygen</c> writes.
/// </summary>
/// <remarks>
/// Stored verbatim, including its header and trailer. Not reformatted, not re-encoded, not normalised:
/// OpenSSH, PKCS#1 and PKCS#8 all round-trip through here untouched, and a client that rewrote them
/// would eventually rewrite one it did not fully understand.
/// </remarks>
public required string PrivateKeyPem { get; init; }
/// <summary>
/// The passphrase protecting the private key, when it has one.
/// </summary>
/// <remarks>
/// <para>
/// Kept with the key rather than typed per connection, which is the entire point of a vault: the
/// passphrase defends the key file on a disk, and inside a vault the key is not on a disk. Storing both
/// together means the vault passphrase is what protects them, which is the guarantee this product is
/// built to make. A user who wants the second factor can leave this null and be prompted.
/// </para>
/// <para>
/// <b>An empty string is normalised to null, so there is exactly one way to say "no passphrase".</b>
/// Two spellings of one state cost more than they look: two clients that agree about a key and disagree
/// only about which spelling they used would produce different payload bytes for an identical key and a
/// spurious field conflict out of the merge, and <c>Passphrase is not null</c> would stop being a
/// reliable answer to "is this key protected?" — which is what the interface reads to describe a key.
/// Normalising here rather than at each call site means every way one can arrive lands on the same
/// value: an editor whose box was left blank, a codec decoding another client's <c>""</c>, a merge
/// picking one side.
/// </para>
/// <para>
/// It is <em>not</em> a defence against SSH.NET, which was the original reason given here and turned out
/// to be false: a passphrase handed to <c>PrivateKeyFile</c> for a key that has none is ignored, not
/// rejected, and the connection succeeds. See docs/platform-flags.md.
/// </para>
/// </remarks>
public string? Passphrase
{
get => passphrase;
init => passphrase = string.IsNullOrEmpty(value) ? null : value;
}
/// <summary>
/// The public half, in <c>authorized_keys</c> form, when it is known.
/// </summary>
/// <remarks>
/// Not derived from the private key, and deliberately optional. Deriving it means parsing every key
/// format this type accepts verbatim, which is the thing above that it declines to do. It is worth
/// keeping because installing a key on a host needs exactly this line, and a user who imported only a
/// private key should be told the public half is missing rather than have one silently reconstructed.
/// </remarks>
public string? PublicKey { get; init; }
/// <summary>Free text.</summary>
public string? Notes { get; init; }
/// <summary>
/// Whether this key is storable, and why not if it is not.
/// </summary>
/// <remarks>
/// The public-key mix-up is checked explicitly because it is the mistake a person actually makes:
/// <c>ssh-keygen</c> writes two files whose names differ by four characters, and pasting the wrong one
/// produces a vault item that looks fine and fails at connection time with an authentication error that
/// says nothing about which file you chose.
/// </remarks>
public bool TryValidate([NotNullWhen(false)] out string? reason)
{
if (string.IsNullOrWhiteSpace(Label))
{
reason = "A key needs a name.";
return false;
}
if (string.IsNullOrWhiteSpace(PrivateKeyPem))
{
reason = "A key needs its private key material.";
return false;
}
var material = PrivateKeyPem.TrimStart();
if (material.StartsWith("ssh-", StringComparison.Ordinal)
|| material.StartsWith("ecdsa-", StringComparison.Ordinal))
{
reason = "That is a public key. Paste the private key — the file without the .pub extension.";
return false;
}
if (!material.StartsWith("-----BEGIN", StringComparison.Ordinal))
{
reason = "That does not look like a private key; it should begin with \"-----BEGIN\".";
return false;
}
reason = null;
return true;
}
}