Public Access
The WebView sat inside the Hosts grid, so navigating to Files or the keychain hid every open terminal and the strip that named them. A connection you had opened was invisible from four of the five screens. The window now has two surfaces rather than one: a nav rail that says which page you are on, and a terminal strip that is always there and switches the whole content area to a shell. Screen keeps meaning "which page" and never becomes a sixth kind of page, which is why this is two properties instead of one enum with a terminal member in it. Every screen lives inside one wrapper panel that collapses when a terminal is showing. That is not tidiness — the WebView hosts a Win32 child window that composites above everything Avalonia draws, so a screen left visible over its rectangle is a screen sliced in half, and this window has shipped that defect once already. One decision point, IsTerminalShowing, and a nested panel rather than five compound bindings nobody would remember to extend. The focus choreography is the part no test in this repo can see. Every reveal path now focuses in the same turn the WebView appeared, so all three of them post at DispatcherPriority.Loaded and let the native control re-push its bounds first. Going the other way had a real bug: the screen-changed branch called a bare Focus() where it had to release the keyboard from the native child, so switching from a terminal to Files silently ate the first keystrokes. Rare before this commit and the primary gesture after it. The tab strip grew a cross inside each tab, a plus that opens the quick-connect palette, and middle-click close. Nested buttons are correct here: Avalonia handles a left press on the cross and deliberately does not handle other buttons, which is exactly what lets middle-click bubble up from the cross as well as the tab. The test is PointerUpdateKind rather than IsMiddleButtonPressed, because the latter reports button state and is also true for a left press made while the middle button happens to be held. The handler is on the tab and not the strip, so the background closes nothing by construction. Plus opens the palette rather than a flyout, since a menu dropping into the WebView's rectangle may or may not composite above a child HWND and this repo does not make rendering claims it has not photographed. Everything a user reads now says keychain. The wire, the database and the cryptographic spec still say vault, deliberately: renaming those is a migration and a protocol change for a word. That split is written down rather than left to be rediscovered as an inconsistency. Four things that were squeezed into the keychain's category rail, or into nothing at all, now have screens. Pinned host keys get one, with fingerprints never truncated and a filter that matches them, because comparing what you have against what the operator published is the whole workflow; the approved date is read out of the item's UUIDv7 rather than added as a column, and says so, since it means first approval and not last use. Keys can be generated in the client, which needed the openssh-key-v1 container written by hand — there is no BCL or NSec helper, and the PKCS#8 route is unverified in the SSH library this uses. The armour carries no passphrase: encrypting it needs bcrypt_pbkdf, which is Blowfish with a swizzle, in a project whose crypto is otherwise entirely libsodium, for a protection the key's own remarks argue is redundant inside a vault. Generation fills the existing editor and stops, so SAVE stays the one thing that writes. ~/.ssh/config can be imported behind a preview that is ticked per row and writes nothing until the button; IdentityFile records the path and imports the key material only on an explicit opt-in, because reading somebody's private key into a vault is precisely the act this product exists to make deliberate. Match blocks and ProxyJump are reported rather than obeyed — one cannot be evaluated statically and the other has nothing behind it to route with, and a preview that implied otherwise would be worse than one that admits it. Files can be dragged in all four directions that are honestly available. Remote to Explorer does not ship and is not pretended to: the shell wants the bytes during the drop, which needs a virtual file and a native COM data object, outside what Avalonia offers. Note for the next person that Avalonia 12 replaced the drag model outright — DataObject and DataFormats are no-op stubs and IDataObject is not in the reference assembly, so every tutorial written for 11 does not compile here. Hosts can be grouped, flat and never nested. A parent id merged as a scalar lets two offline clients each re-parent A under B and B under A, producing a cycle inside an encrypted payload that no server can police and every reader would have to detect for ever. Membership lives in that payload rather than in the one plaintext concession ADR 0001 allows, whose test is that the relay cannot function without it — nothing on the server reads a group, so what plaintext would hand over is a clustering of the estate for nothing. The plaintext column reserved for it is dropped, provably always null, and the server now refuses a client that sends one; it was never populated, was copied on apply, and was not cleared on delete, so a group id would have outlived the host it described. Snippets insert through xterm rather than through the pump, because xterm is the only thing that knows whether the remote has bracketed paste on, and that is what makes a shell treat embedded newlines as text instead of as execute. The host process moves opaque bytes and never parses output, so it would have to guess, and guessing wrong runs every line. Running is off by default and the copy says the text goes into whatever is there — the terminal has no notion of being at a prompt, and may be in vi or at a password prompt with echo off, so the Enter the user presses themselves is the entire safety property. Connections and keychain changes are recorded as synced encrypted items, which is what makes them auditable by a team later and costs the server knowledge of connection rate and timing from row counts alone. ADR 0001 already concedes it cannot hide that class of metadata; the trade is now written into it rather than left implicit. A connection entry is written once, at close, which is what makes a synced log tractable: nothing to merge, one outbox row, no chance of colliding with itself. Live sessions come from memory, not from the log. The write is void by contract and posts to a bounded channel, because putting an encrypt-and-write on the teardown path of every session is how closing the application comes to take four seconds. A ticket opened before a lock still closes afterwards, since a shell outlives the vault. The activity log hooks the one generic repository every kind writes through, so it cannot miss a caller — which is also why the log kinds themselves declare they are not audited, or the first entry would write an entry about writing an entry. It records the names of the fields that changed and never their values; a log with an old password in it would be a plaintext credential store with no vault around it. Retention is 90 days or 5,000 entries, whichever bites first, pruned on the sync loop rather than on a second timer. That log traffic then broke the status line, which is worth recording because the fix is a shape and not a patch: background sync counted its own log rows as pushed items, so the quiet rule stopped being quiet and every action's message was overwritten a second later by a sync report. The report now separates log rows from user items and the rule reads the latter. S3 buckets appear as a remote in the file browser, behind the same interface an SFTP session implements, so the queue and both panes did not have to learn what they are talking to. Uploads go through a pipe, because the queue wants to write and the SDK wants to read; memory is then bounded by the part size instead of buffering a file to disk twice. Finally, the Windows device key store moved out of the session project, which was the one thing keeping it from being portable — everything else in it is platform-neutral, and a Windows CNG dependency in the middle of the vault code meant a second head could not reference it without dragging Windows along. The seam that made the move free was already there. docs/android-port.md is the audit behind that: what ports, what does not, in order of cost, the four decisions taken, and an inventory of every screen and state the interface has to carry, written so a design can be made from it directly. dotnet build, dotnet test and dotnet format --verify-no-changes are all clean: 1240 tests at zero warnings, including the end-to-end suite against real containers. The manual checks that headless Avalonia cannot make — the drag from Explorer, a generated key against a real host, twelve tabs at the minimum window width — are listed in docs/manual-checks.md and are still outstanding.
385 lines
16 KiB
C#
385 lines
16 KiB
C#
using System.Security.Cryptography;
|
|
using DodoSSH.Client.Domain;
|
|
using DodoSSH.Client.Sync;
|
|
using DodoSSH.Contracts;
|
|
using DodoSSH.Crypto;
|
|
|
|
namespace DodoSSH.Client.Sync.Tests;
|
|
|
|
/// <summary>
|
|
/// Each item type must be sealed under its own AAD resource type, and the two enums that name item types
|
|
/// deliberately do not agree.
|
|
/// </summary>
|
|
/// <remarks>
|
|
/// <para>
|
|
/// <c>SyncEntityType</c> lists only syncable items, so <c>Host</c> is 1 and <c>SshKey</c> is 3.
|
|
/// <c>CryptoSpec.AadResourceType</c> also covers users, devices and vaults, so the same two are 4 and 6. A
|
|
/// cipher written by copying its neighbour and casting the wire type would therefore seal a private key as
|
|
/// if it were a vault — encrypting cleanly, decrypting cleanly on the machine that wrote it, and violating
|
|
/// docs/crypto.md in a way that surfaces only when another implementation reads the item.
|
|
/// </para>
|
|
/// <para>
|
|
/// These tests are cheap and the alternative is a comment. The payload's AAD is frozen, so getting this
|
|
/// wrong is not something a later release can quietly correct: only clients can re-encrypt, and they can
|
|
/// only do it if they can still open what is there.
|
|
/// </para>
|
|
/// </remarks>
|
|
public sealed class AadResourceTypeTests
|
|
{
|
|
/// <remarks>
|
|
/// The pairing stated as a table. If <c>AadResourceType</c> is ever renumbered, this is what says so —
|
|
/// loudly, and before anything is written under the new numbers.
|
|
/// </remarks>
|
|
[Theory]
|
|
[InlineData(SyncEntityType.Host, CryptoSpec.AadResourceType.Host)]
|
|
[InlineData(SyncEntityType.Credential, CryptoSpec.AadResourceType.Credential)]
|
|
[InlineData(SyncEntityType.SshKey, CryptoSpec.AadResourceType.SshKey)]
|
|
[InlineData(SyncEntityType.HostGroup, CryptoSpec.AadResourceType.HostGroup)]
|
|
[InlineData(SyncEntityType.Tag, CryptoSpec.AadResourceType.Tag)]
|
|
[InlineData(SyncEntityType.Snippet, CryptoSpec.AadResourceType.Snippet)]
|
|
[InlineData(SyncEntityType.PortForward, CryptoSpec.AadResourceType.PortForward)]
|
|
[InlineData(SyncEntityType.KnownHostKey, CryptoSpec.AadResourceType.KnownHostKey)]
|
|
[InlineData(SyncEntityType.ConnectionLogEntry, CryptoSpec.AadResourceType.ConnectionLogEntry)]
|
|
[InlineData(SyncEntityType.ActivityLogEntry, CryptoSpec.AadResourceType.ActivityLogEntry)]
|
|
[InlineData(SyncEntityType.ObjectStore, CryptoSpec.AadResourceType.ObjectStore)]
|
|
public void TheTwoEnums_AreNamedAlikeAndNumberedDifferently(
|
|
SyncEntityType wire,
|
|
CryptoSpec.AadResourceType resource)
|
|
{
|
|
Enum.GetName(wire).ShouldBe(Enum.GetName(resource));
|
|
|
|
// The point of the whole file: same name, different number. A test asserting equality here would be
|
|
// asserting the bug.
|
|
((int)wire).ShouldNotBe(
|
|
(int)resource,
|
|
$"{wire} happens to share a value with its resource type, which makes a cast look correct. "
|
|
+ "Either the enums were renumbered or this pairing needs re-checking by hand.");
|
|
}
|
|
|
|
/// <summary>
|
|
/// The specified pairing of wire type to AAD resource type, stated out of band, one row per cipher.
|
|
/// </summary>
|
|
/// <remarks>
|
|
/// The single source for both tests below: what each cipher must use, and which types must have a cipher
|
|
/// pinned at all. Adding an item type without adding a row here fails
|
|
/// <see cref="EverySynchronisedType_HasItsCipherPinnedHere"/>.
|
|
/// </remarks>
|
|
private static readonly (SyncEntityType Wire, CryptoSpec.AadResourceType Resource)[] PinnedPairs =
|
|
[
|
|
(SyncEntityType.Host, CryptoSpec.AadResourceType.Host),
|
|
(SyncEntityType.SshKey, CryptoSpec.AadResourceType.SshKey),
|
|
(SyncEntityType.Credential, CryptoSpec.AadResourceType.Credential),
|
|
(SyncEntityType.KnownHostKey, CryptoSpec.AadResourceType.KnownHostKey),
|
|
(SyncEntityType.HostGroup, CryptoSpec.AadResourceType.HostGroup),
|
|
(SyncEntityType.Snippet, CryptoSpec.AadResourceType.Snippet),
|
|
(SyncEntityType.ConnectionLogEntry, CryptoSpec.AadResourceType.ConnectionLogEntry),
|
|
(SyncEntityType.ActivityLogEntry, CryptoSpec.AadResourceType.ActivityLogEntry),
|
|
(SyncEntityType.ObjectStore, CryptoSpec.AadResourceType.ObjectStore),
|
|
];
|
|
|
|
public static TheoryData<SyncEntityType, CryptoSpec.AadResourceType> Pinned
|
|
{
|
|
get
|
|
{
|
|
var data = new TheoryData<SyncEntityType, CryptoSpec.AadResourceType>();
|
|
|
|
foreach (var (wire, resource) in PinnedPairs)
|
|
{
|
|
data.Add(wire, resource);
|
|
}
|
|
|
|
return data;
|
|
}
|
|
}
|
|
|
|
/// <remarks>
|
|
/// <para>
|
|
/// Opened <em>independently</em>, through the low-level <c>ItemKeys</c> API with the resource type this
|
|
/// table names rather than the one the cipher holds. That is the whole point, and it is the property two
|
|
/// earlier versions of this file lacked: checking that a key payload does not open as a host is true
|
|
/// however both ciphers are misconfigured, because <c>Seal</c> and <c>TryOpen</c> share one constant. A
|
|
/// test that compares an implementation against itself cannot catch a self-consistent mistake.
|
|
/// </para>
|
|
/// <para>
|
|
/// Written as a table over every cipher, not one test per cipher, because the same hole was found three
|
|
/// times — twice by mutation testing after the fact. Pointing <c>CredentialCipher</c> at
|
|
/// <c>AadResourceType.Vault</c> passed the entire suite until this existed.
|
|
/// </para>
|
|
/// </remarks>
|
|
[Theory]
|
|
[MemberData(nameof(Pinned))]
|
|
public void EveryCipher_SealsUnderTheResourceTypeTheSpecificationNames(
|
|
SyncEntityType wire,
|
|
CryptoSpec.AadResourceType resource)
|
|
{
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
const uint Generation = 1;
|
|
const uint Version = 1;
|
|
|
|
var payload = SealSample(wire, vaultKey, entityId, Generation, (int)Version);
|
|
|
|
var dataKey = ItemKeys.TryUnwrapDataKey(
|
|
vaultKey, payload.WrappedDataKey, resource, entityId, Generation, Version);
|
|
|
|
dataKey.ShouldNotBeNull(
|
|
$"The {wire} cipher must wrap its data key under AadResourceType.{resource}; a null here means "
|
|
+ "it used some other resource type, which round-trips fine and violates docs/crypto.md.");
|
|
|
|
ItemKeys.TryOpenPayload(
|
|
dataKey,
|
|
payload.Envelope,
|
|
resource,
|
|
entityId,
|
|
payload.DataKeyId,
|
|
Generation,
|
|
Version).ShouldNotBeNull("and it must seal the envelope under the same resource type.");
|
|
}
|
|
|
|
/// <remarks>
|
|
/// The guard that makes the table above self-maintaining. A fourth item type would otherwise sync,
|
|
/// encrypt and merge correctly while being sealed under any resource type at all, and nothing would say
|
|
/// so until another implementation refused the item — by which point the AAD is frozen into stored
|
|
/// ciphertext and only clients can re-encrypt it.
|
|
/// </remarks>
|
|
[Fact]
|
|
public void EverySynchronisedType_HasItsCipherPinnedHere()
|
|
{
|
|
PinnedPairs.Select(pair => pair.Wire)
|
|
.ShouldBe(ItemKinds.SyncedTypes, ignoreOrder: true);
|
|
}
|
|
|
|
private static EncryptedPayload SealSample(
|
|
SyncEntityType wire,
|
|
byte[] vaultKey,
|
|
Guid entityId,
|
|
uint generation,
|
|
int version) => wire switch
|
|
{
|
|
SyncEntityType.Host => HostCipher.Seal(
|
|
new HostSecret { Label = "prod-db", Hostname = "db.internal" },
|
|
vaultKey,
|
|
entityId,
|
|
generation,
|
|
version),
|
|
|
|
SyncEntityType.SshKey => SshKeyCipher.Seal(
|
|
NewKey(), vaultKey, entityId, generation, version),
|
|
|
|
SyncEntityType.Credential => CredentialCipher.Seal(
|
|
NewCredential(), vaultKey, entityId, generation, version),
|
|
|
|
SyncEntityType.KnownHostKey => KnownHostKeyCipher.Seal(
|
|
NewKnownHost(), vaultKey, entityId, generation, version),
|
|
|
|
SyncEntityType.HostGroup => HostGroupCipher.Seal(
|
|
NewGroup(), vaultKey, entityId, generation, version),
|
|
|
|
SyncEntityType.Snippet => SnippetCipher.Seal(
|
|
NewSnippet(), vaultKey, entityId, generation, version),
|
|
|
|
SyncEntityType.ConnectionLogEntry => ConnectionLogCipher.Seal(
|
|
NewConnectionEntry(), vaultKey, entityId, generation, version),
|
|
|
|
SyncEntityType.ActivityLogEntry => ActivityLogCipher.Seal(
|
|
NewActivityEntry(), vaultKey, entityId, generation, version),
|
|
|
|
SyncEntityType.ObjectStore => ObjectStoreCipher.Seal(
|
|
NewBucket(), vaultKey, entityId, generation, version),
|
|
|
|
_ => throw new ArgumentOutOfRangeException(
|
|
nameof(wire),
|
|
wire,
|
|
"No sample exists for this item type. Add one when adding the type, or the pairing above "
|
|
+ "cannot be checked."),
|
|
};
|
|
|
|
[Fact]
|
|
public void ACredentialPayload_OpensAsNothingElse()
|
|
{
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
|
|
var sealed_ = CredentialCipher.Seal(
|
|
NewCredential(), vaultKey, entityId, keyGeneration: 1, itemVersion: 1);
|
|
|
|
HostCipher.TryOpen(sealed_, vaultKey, entityId, itemVersion: 1).ShouldBeNull();
|
|
SshKeyCipher.TryOpen(sealed_, vaultKey, entityId, itemVersion: 1).ShouldBeNull();
|
|
CredentialCipher.TryOpen(sealed_, vaultKey, entityId, itemVersion: 1).ShouldNotBeNull();
|
|
}
|
|
|
|
[Fact]
|
|
public void ACredentialSealedAtOneVersion_DoesNotOpenAtAnother()
|
|
{
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
|
|
var payload = CredentialCipher.Seal(
|
|
NewCredential(), vaultKey, entityId, keyGeneration: 1, itemVersion: 2);
|
|
|
|
CredentialCipher.TryOpen(payload, vaultKey, entityId, itemVersion: 3).ShouldBeNull();
|
|
}
|
|
|
|
[Fact]
|
|
public void AKeyPayload_DoesNotOpenAsAHost()
|
|
{
|
|
// Weaker than the two above and kept anyway: it is the property a reader expects to see, and it
|
|
// covers the case where one cipher is corrected and the other is not.
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
|
|
var sealedKey = SshKeyCipher.Seal(NewKey(), vaultKey, entityId, keyGeneration: 1, itemVersion: 1);
|
|
|
|
HostCipher.TryOpen(sealedKey, vaultKey, entityId, itemVersion: 1).ShouldBeNull();
|
|
SshKeyCipher.TryOpen(sealedKey, vaultKey, entityId, itemVersion: 1).ShouldNotBeNull();
|
|
}
|
|
|
|
[Fact]
|
|
public void AHostPayload_DoesNotOpenAsAKey()
|
|
{
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
|
|
var host = new HostSecret { Label = "prod-db", Hostname = "db.internal" };
|
|
var sealedHost = HostCipher.Seal(host, vaultKey, entityId, keyGeneration: 1, itemVersion: 1);
|
|
|
|
SshKeyCipher.TryOpen(sealedHost, vaultKey, entityId, itemVersion: 1).ShouldBeNull();
|
|
}
|
|
|
|
[Fact]
|
|
public void AKey_RoundTripsThroughTheCipher()
|
|
{
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
var key = NewKey();
|
|
|
|
var payload = SshKeyCipher.Seal(key, vaultKey, entityId, keyGeneration: 1, itemVersion: 3);
|
|
var opened = SshKeyCipher.TryOpen(payload, vaultKey, entityId, itemVersion: 3);
|
|
|
|
opened.ShouldNotBeNull();
|
|
opened.Key.ShouldBe(key);
|
|
opened.SchemaVersion.ShouldBe(SshKeySecretCodec.CurrentSchemaVersion);
|
|
opened.IsReadOnly.ShouldBeFalse();
|
|
}
|
|
|
|
[Fact]
|
|
public void AKeySealedAtOneVersion_DoesNotOpenAtAnother()
|
|
{
|
|
// The item version is in the AAD, which is what stops a server rolling a row back to earlier
|
|
// ciphertext. Asserted for keys as well as hosts because it is the property most easily lost by
|
|
// copying a cipher and adjusting the wrong argument.
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
|
|
var payload = SshKeyCipher.Seal(NewKey(), vaultKey, entityId, keyGeneration: 1, itemVersion: 2);
|
|
|
|
SshKeyCipher.TryOpen(payload, vaultKey, entityId, itemVersion: 3).ShouldBeNull();
|
|
}
|
|
|
|
[Fact]
|
|
public void AKnownHostPayload_OpensAsNothingElse()
|
|
{
|
|
// The pairing table above is the load-bearing check; this is the cross-type refusal a reader expects
|
|
// to see spelled out, and it is the one that would notice a second cipher being pointed at
|
|
// AadResourceType.KnownHostKey by mistake.
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
|
|
var sealed_ = KnownHostKeyCipher.Seal(
|
|
NewKnownHost(), vaultKey, entityId, keyGeneration: 1, itemVersion: 1);
|
|
|
|
HostCipher.TryOpen(sealed_, vaultKey, entityId, itemVersion: 1).ShouldBeNull();
|
|
SshKeyCipher.TryOpen(sealed_, vaultKey, entityId, itemVersion: 1).ShouldBeNull();
|
|
CredentialCipher.TryOpen(sealed_, vaultKey, entityId, itemVersion: 1).ShouldBeNull();
|
|
KnownHostKeyCipher.TryOpen(sealed_, vaultKey, entityId, itemVersion: 1).ShouldNotBeNull();
|
|
}
|
|
|
|
[Fact]
|
|
public void AKnownHostSealedAtOneVersion_DoesNotOpenAtAnother()
|
|
{
|
|
var vaultKey = RandomNumberGenerator.GetBytes(32);
|
|
|
|
var entityId = Guid.CreateVersion7();
|
|
|
|
var payload = KnownHostKeyCipher.Seal(
|
|
NewKnownHost(), vaultKey, entityId, keyGeneration: 1, itemVersion: 2);
|
|
|
|
KnownHostKeyCipher.TryOpen(payload, vaultKey, entityId, itemVersion: 3).ShouldBeNull();
|
|
}
|
|
|
|
private static ConnectionLogSecret NewConnectionEntry() => new()
|
|
{
|
|
HostLabel = "prod-db",
|
|
Address = "deploy@db.internal:22",
|
|
HostId = Guid.CreateVersion7(),
|
|
StartedAt = new DateTimeOffset(2026, 7, 31, 9, 15, 0, TimeSpan.Zero),
|
|
Duration = TimeSpan.FromMinutes(11),
|
|
Outcome = ConnectionOutcome.Closed,
|
|
DeviceName = "laptop",
|
|
ActorUserId = Guid.CreateVersion7(),
|
|
};
|
|
|
|
private static ActivityLogSecret NewActivityEntry() => new()
|
|
{
|
|
ItemKind = nameof(SyncEntityType.Host),
|
|
ItemId = Guid.CreateVersion7(),
|
|
ItemLabel = "prod-db",
|
|
Operation = ActivityOperation.Updated,
|
|
ChangedFields = "Port, Username",
|
|
At = new DateTimeOffset(2026, 7, 31, 9, 15, 0, TimeSpan.Zero),
|
|
DeviceName = "laptop",
|
|
ActorUserId = Guid.CreateVersion7(),
|
|
};
|
|
|
|
private static ObjectStoreSecret NewBucket() => new()
|
|
{
|
|
Label = "backups",
|
|
Bucket = "dodossh-backups",
|
|
AccessKeyId = "AKIAEXAMPLE",
|
|
SecretAccessKey = "an example secret access key",
|
|
Region = "eu-west-1",
|
|
};
|
|
|
|
private static HostGroupSecret NewGroup() => new() { Label = "production" };
|
|
|
|
private static SnippetSecret NewSnippet() => new()
|
|
{
|
|
Label = "restart the api",
|
|
Command = "sudo systemctl restart dodossh-api",
|
|
Notes = "checked with the on-call rota first",
|
|
};
|
|
|
|
private static KnownHostSecret NewKnownHost() => new()
|
|
{
|
|
Host = "db.internal",
|
|
Port = 22,
|
|
Algorithm = "ssh-ed25519",
|
|
Fingerprint = "SHA256:5cWZ1Zc2ZmEXAMPLEfingerprintvalue0123456789a",
|
|
};
|
|
|
|
private static CredentialSecret NewCredential() => new()
|
|
{
|
|
Label = "db-login",
|
|
Password = "hunter2",
|
|
Username = "postgres",
|
|
Notes = "used by CI",
|
|
};
|
|
|
|
private static SshKeySecret NewKey() => new()
|
|
{
|
|
Label = "deploy",
|
|
PrivateKeyPem = "-----BEGIN OPENSSH PRIVATE KEY-----\nnot-a-real-key\n-----END OPENSSH PRIVATE KEY-----",
|
|
Passphrase = "a passphrase",
|
|
PublicKey = "ssh-ed25519 AAAAC3Nz deploy@example",
|
|
Notes = "used by CI",
|
|
};
|
|
}
|