The empty row's "8080" placeholders looked like a typed 8080 -> 8080, and
+ Add saved it as 0 -> 0 at once; a project refresh with a new-but-equal
array also reset in-progress edits. The editor now keeps ports as text,
saves only complete rows, marks incomplete ones inline, uses word
placeholders, and resyncs only on a by-value change while unfocused. A
connect reports a stored incomplete row as a ports warning.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Port mappings (AWS):
- In the workspace each connection now picks 127.0.0.1 or [::1] from
/proc/net/tcp{,6} (tunnel::mapping_command): a server bound to ::1 only
(Vite, Node `localhost`) was unreachable through a mapping. No probe
connection is made; nothing found falls back to 127.0.0.1.
- The first socat "Connection refused" per mapping is a `ports`
workspace-warning: "nothing is listening on port N in the workspace
(127.0.0.1 or ::1)".
- open_for_project warns instead of returning None when a Running project's
mappings can't be opened (no tunnel, or the tunnel changed under the open).
- Info/warn logs at each step (mappings read, each opened/failed, set closed
and why) so the next report shows where it stopped.
- Tests: start-path sequence (mapping saved while stopped, tunnel, Running,
open) with IPv4 and ::1 clients; refusal reported once; never-silent cases;
an ignored live test against a real agent container (0.0.0.0, [::1] and
nothing-listening servers).
Silent agent: the error now says the image (named, escaped) may predate the
app's AWS support, that :latest moves only on a release, and to set
Settings → Docker → Custom image to ghcr.io/shadowdao/triple-c-sandbox:edge.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The app told a user whose Docker daemon had hit systemd start-limit-hit
to install Docker. New check_docker_status command classifies the ping
failure (io error kind in the bollard/hyper chain) plus cheap installed-
ness probes into running / not_running / no_permission / not_installed,
reports the endpoint tried (DOCKER_HOST respected), and the dialog, top
bar, welcome checklist and Docker settings show per-state guidance. The
dialog updates live from polling and closes when Docker comes up.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Runs carry an explicit kind (deploy, follow, repair, update, destroy,
onboard, push, boundary); the admin-bundle offer after an AWS refusal
keys on kind deploy/onboard, not the label, so a refused follow of an
existing environment's deploy no longer offers a new-environment bundle.
- looksDenied no longer matches a bare "explicit deny" (SCP and bucket
policy denies aren't fixed by a bundle); the hint says it may need an admin.
- The aws sso login hint breaks long profile names.
- The "Not an admin?" disclosure shows a ▸/▾ marker like the Environments
toggle.
- Note: the previous commit's Modal footer flex-wrap is app-wide (every
modal's buttons now wrap when the dialog is narrow); kept deliberately.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hosts settings live in a 224-320px sidebar; nowrap buttons and long ARNs,
policy names and run summaries overflowed it. Button and StatusIndicator get
an opt-in wrap prop; host, environment, progress and policy rows wrap with
min-w-0 children; policy copy buttons sit in an auto-fill grid; pre blocks
scroll; the Modal footer wraps.
Deploy a new environment and self-join are offered to anyone after a scan.
When the permission check didn't confirm environment-admin rights a note
says AWS has the last word, and the policies and environment request sit
under a 'Not an admin?' disclosure. The boundary note shows whenever the
boundary is missing. AWS refusals show AWS's message (awsErrorMessage now
names the denied action) and offer the admin bundle: in the deploy and join
modals, and under a failed deploy/join run whose output reads as denied.
The backend already had no tier check on onboard_aws_user; its comment is
corrected.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The short %SystemDrive%\ssm-<8hex> root inherited the drive root's ACL,
where Authenticated Users can write, so another local user could swap the
source, toolchain or output between verification and use. Right after
creating it, icacls removes inheritance and grants full control only to
SYSTEM, Administrators and the current user's SID; failure aborts. It is
mandatory on Windows and skipped only off Windows (the pwsh test path).
The binary is hashed again at its final location.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- build-ssm-plugin.{sh,ps1}: skip the vendored SDK's Java codegen/ and
test snapshot/ trees when extracting (codegen paths reach 258 chars,
past MAX_PATH on Windows); the .ps1 works under a short
%SystemDrive%\ssm-<8hex> root and falls back to rd /s /q on cleanup.
Pinned output hashes unchanged (rebuilt every target).
- build-ssm-plugin.sh: the header no longer claims a git commit-id check.
- windows-verify-signatures.ps1: compare signer Subject + Issuer, not the
thumbprint (Artifact Signing certificates rotate); require
THIRD_PARTY_NOTICES in the MSI.
- windows-sign.ps1: allowlist exactly
src-tauri\binaries\session-manager-plugin-x86_64-pc-windows-msvc.exe.
- macOS jobs: check the .app carries the two-slice plugin and
Contents/Resources/THIRD_PARTY_NOTICES.
- CLAUDE.md: a local release build must re-run the build script.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AWS ships its prebuilt plugin as "AWS Content" under the AWS Customer
Agreement; the source is Apache-2.0. Replace the binary fetch with
scripts/build-ssm-plugin.sh (any triple, cross-compiles; universal via
lipo) and build-ssm-plugin.ps1 (Windows runner):
- source: tag 1.2.896.0 at commit 6430675a, GitHub archive SHA-256
checked before extraction;
- Go 1.26.11 from go.dev, published SHA-256 checked before use;
- the repo's own build (GOPATH mode, vendored deps, -s -w,
sessionmanagerplugin-main) with VERSION stamped to the tag, plus
-trimpath, no VCS stamp, empty build id, CGO off;
- output must equal a pinned SHA-256 per target (reproducible builds).
Each platform job builds its own targets. Windows: the exe is now ours
and unsigned, so windows-sign.ps1 allowlists it and
windows-verify-signatures.ps1 requires it signed by the installer's own
certificate in the MSI and NSIS. THIRD_PARTY_NOTICES now carries the
source's LICENSE/NOTICE/THIRD-PARTY, the commit, every linked vendored
module's licence and Go's. AWS's GPG key and the AWS-signature checks
are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both build workflows fetch the pinned plugin before tauri build on Linux,
macOS (universal: both slices plus the lipo'd file) and Windows. The test
job needs no fetch: debug builds get build.rs's placeholder.
finalize-appimage.sh asserts usr/bin/session-manager-plugin is a running
ELF and THIRD_PARTY_NOTICES is in the image.
Windows: the plugin ships under AWS's Authenticode signature and is not
re-signed (Tauri skips a sidecar signtool verify accepts).
windows-sign.ps1 refuses it if it is ever presented rather than letting the
allowlist skip it unsigned; windows-verify-signatures.ps1 requires it in
the MSI, valid, timestamped and signed by Amazon Web Services, Inc.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bundle.externalBin ships the plugin beside the app binary (usr/bin in the
AppImage, Contents/MacOS, the Windows install dir) and THIRD_PARTY_NOTICES as
a resource. find_plugin() now resolves TRIPLEC_SSM_PLUGIN, then the bundled
sidecar next to current_exe(), then PATH and AWS's install locations, then
the install hint; the order is unit-tested against temp dirs.
tauri-build fails any build whose externalBin file is missing, so build.rs
writes a marked placeholder in debug builds (cargo test/check, tauri dev)
and refuses a missing file or a placeholder in release builds.
find_plugin() skips the placeholder.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/fetch-ssm-plugin.sh (Linux/macOS, incl. universal via lipo) and
scripts/fetch-ssm-plugin.ps1 (Windows) download plugin 1.2.896.0 from AWS's
S3 path into app/src-tauri/binaries/session-manager-plugin-<triple>[.exe],
checking a pinned SHA-256 of each artifact before extraction, AWS's GPG
signature on the Linux .deb (key committed, fingerprint pinned) or AWS's
Authenticode signature on Windows, and a pinned SHA-256 of the binary.
THIRD_PARTY_NOTICES reproduces the plugin's LICENSE (Apache-2.0), NOTICE
and AWS's THIRD-PARTY statement. The binaries directory is never committed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>