lotobo/toolbox-portal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 32 Wiki Activity

feat: add OTP and Passkey Tools to Toolbox 0.11.0

Browse Source
This commit is contained in:
zemion
2026-08-19 12:20:27 +02:00
parent 5ed7134d42
commit 0baeda8be8
19 changed files with 188 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+31 -18
View File
@@ -1,7 +1,7 @@
# add·ideas Toolbox Portal
`toolbox-portal` is the static launcher and release assembler for the add·ideas
browser toolbox. Version `0.2.12` reads one same-origin catalogue, shows each app
browser toolbox. Version `0.2.13` reads one same-origin catalogue, shows each app
as a compact launch tile, and keeps personal pins, drag-and-drop ordering,
visibility, and appearance in the current browser. Pinned tools have their own
section; search, category, and clickable tag filters stay close to the tool
@@ -37,7 +37,7 @@ the SDK and portal together.
Vite uses `base: './'`, so the built portal works at `/` or a nested static path.
The development catalogue at `public/toolbox.catalog.json` points to assembled
paths (`./apps/pdf/`, `./apps/xslt/`, `./apps/onenote/`, `./apps/av/`,
`./apps/regex/`, and `./apps/svg/`).
`./apps/regex/`, `./apps/svg/`, and `./apps/auth/`).
Those manifests will correctly appear as unavailable until an assembled release
is being served.
@@ -69,7 +69,7 @@ privacy and executable-code warning. Light, dark, and system modes are supported
## Production deployment behind Traefik
The committed `compose.yaml` is the shortest production path. Its release
container downloads the immutable Toolbox 0.10.0 ZIP during the image build,
container downloads the immutable Toolbox 0.11.0 ZIP during the image build,
verifies SHA-256 before extracting it, and then copies only the verified static
files into the pinned unprivileged nginx image. Node.js and a local portal
assembly are not required on the deployment host.
@@ -80,7 +80,7 @@ Prerequisites:
- Traefik attached to the existing external Docker network `internal`;
- Traefik HTTP and HTTPS entrypoints named `web` and `websecure`;
- a certificate resolver named `netcup`;
- DNS for `toolbox.add-ideas.de` pointing to that Traefik instance; and
- DNS for `toolbox.add-ideas.de` and `auth.toolbox.add-ideas.de` pointing to that Traefik instance; and
- outbound HTTPS access to `git.add-ideas.de` while the image is built.
Deploy a fresh clone with:
@@ -100,6 +100,16 @@ release version, and matching checksum can be overridden through environment
variables; copy `.env.example` to `.env` only when an override is needed. For
example, set `TOOLBOX_HOST=staging.toolbox.add-ideas.de` for a staging host.
The same container also exposes only the packaged authentication app at
`https://auth.toolbox.add-ideas.de/`. Traefik adds the internal `/apps/auth`
prefix while the public URL remains `/`, so assets remain relative and the browser
binds WebAuthn credentials to the dedicated `auth.toolbox.add-ideas.de` RP ID.
The main Toolbox copy at `/apps/auth/` remains useful for offline inspection but
disables live ceremonies because all Portal apps share that origin. The router
hostname can be overridden with `AUTH_TOOLS_HOST`, but auth-tools 0.1.0 enables
live ceremonies only on its pinned production host (or localhost); other hosts
remain inspect-only. Never widen the RP ID to `add-ideas.de`.
The external network is deliberately not created by this project. Creating a
private project-local network would prevent an independently managed Traefik
container from reaching the service.
@@ -121,9 +131,10 @@ The app release should also publish a matching `.sha256` sidecar. The manifest
must declare the pinned reverse-DNS id and version. Application and portal
versions are independent.
`release/toolbox.lock.json` is the reviewed v0.10.0 lock. Its URLs and checksums
`release/toolbox.lock.json` is the reviewed v0.11.0 lock. Its URLs and checksums
pin the published PDF Tools 0.4.4, XSLT Tools 0.4.3, OneNote Tools 0.3.4,
Audio & Video Tools 0.3.0, Regex Tools 0.4.2, and SVG Tools 0.1.0 release bytes. Use
Audio & Video Tools 0.3.0, Regex Tools 0.4.2, SVG Tools 0.1.0, and OTP & Passkey
Tools 0.1.0 release bytes. Use
`release/toolbox.lock.example.json` as the template for a future release and
verify every downloaded asset before committing updated values. Artifacts may be:
@@ -144,7 +155,7 @@ npm run assemble -- \
--lock release/toolbox.lock.json \
--portal-dist dist \
--output build/toolbox \
--archive build/add-ideas-toolbox-0.10.0.zip
--archive build/add-ideas-toolbox-0.11.0.zip
```
Existing output is refused. Pass `--force` only when replacing those exact
@@ -165,10 +176,11 @@ build/toolbox/
├── onenote/
├── av/
├── regex/
└── svg/
├── svg/
└── auth/
build/add-ideas-toolbox-0.10.0.zip
build/add-ideas-toolbox-0.10.0.zip.sha256
build/add-ideas-toolbox-0.11.0.zip
build/add-ideas-toolbox-0.11.0.zip.sha256
```
The assembler verifies SHA-256 before opening an artifact, validates every app
@@ -189,7 +201,7 @@ directory separately:
```sh
npm run package:static -- \
--input build/toolbox \
--output artifacts/add-ideas-toolbox-0.10.0.zip
--output artifacts/add-ideas-toolbox-0.11.0.zip
```
This also emits a `.sha256` sidecar.
@@ -210,9 +222,9 @@ normal local XML/XSLT transformations do not require that permission.
```sh
podman build -f Containerfile \
-t git.add-ideas.de/lotobo/toolbox:0.10.0 .
-t git.add-ideas.de/lotobo/toolbox:0.11.0 .
podman run --rm -p 8080:8080 \
git.add-ideas.de/lotobo/toolbox:0.10.0
git.add-ideas.de/lotobo/toolbox:0.11.0
```
For a direct-port local deployment after assembly, use the separate example:
@@ -229,8 +241,8 @@ docker login git.add-ideas.de
docker buildx build \
--platform linux/amd64,linux/arm64 \
--file Containerfile.release \
--tag git.add-ideas.de/lotobo/toolbox:0.10.0 \
--tag git.add-ideas.de/lotobo/toolbox:0.10 \
--tag git.add-ideas.de/lotobo/toolbox:0.11.0 \
--tag git.add-ideas.de/lotobo/toolbox:0.11 \
--push .
```
@@ -252,11 +264,11 @@ needs permission to push code, releases, and container packages to
3. Verify downloaded app assets with `sha256sum -c <asset>.sha256`; copy those
exact values into a reviewed toolbox lock.
4. Run the assembler and serve `build/toolbox` from a nested test path. Open
all six apps, switch between them, and confirm the encoded `toolbox`
all seven apps, switch between them, and confirm the encoded `toolbox`
context.
5. Verify the distribution with
`(cd build && sha256sum -c add-ideas-toolbox-0.10.0.zip.sha256)`.
6. Commit the reviewed lock, tag the toolbox release (for example `v0.10.0`), and
`(cd build && sha256sum -c add-ideas-toolbox-0.11.0.zip.sha256)`.
6. Commit the reviewed lock, tag the toolbox release (for example `v0.11.0`), and
push the branch and tag to Gitea.
7. In Gitea, open **Releases → New release**, select the tag, and upload the
static ZIP plus its `.sha256` file. Do not use a mutable “latest” URL in a
@@ -279,6 +291,7 @@ must not re-resolve app versions or substitute a newer release.
| **`av-tools`** | Existing local-first v0.3.0 release; dedicated repository | Convert and lightly edit audio and video locally in the browser | Immediate native playback and basic file information; progressive stream inspection on demand; quick conversion; trim, split and crossfade concatenate; crop, resize, normalize, fades, waveform, metadata, chapters, subtitles, scene thumbnails/contact sheets, presets and export | Reviewed ffmpeg.wasm 0.12.10 ST/MT build with verified Opus and bundled label font; bounded queue, temporary storage and resource policy; isolation enables MT with automatic ST fallback; versioned core assets are immutable |
| **`regex-tools`** | Current local-first v0.4.2 release; dedicated repository | Develop, explain, test and apply JavaScript, PCRE2, PHP, Perl, Python, Ruby, Java, C++, Go, .NET, Rust and Scala/JVM-compatible regular expressions | Deterministic syntax trees; engine-native matching, captures and bounded replacement; stable double-buffered live results; PCRE2 tracing and C17 generation; comparison; corpus apply; tests; risk/growth/benchmark analysis; generated cases; bounded minimization; validated ECMAScript formatting; project import/export and optional local persistence | Open-source regexpp and pinned local WebAssembly runtimes for PCRE2, PHP preg, legacy Perl, CPython, CRuby, TeaVM Java/Scala compatibility, libc++ C++, Go, .NET and Rust in killable workers; explicit source/licence inventories, resource limits and engine-specific offset semantics |
| **`svg-tools`** | Initial local-first v0.1.0 release; dedicated repository | Inspect and edit SVG source, structure, geometry, references and accessibility locally | Synchronized source/tree/canvas/inspector; path and transform tools; reference analysis; optimization; CSS animation preview; exact, sanitized, raster and project export | Untrusted SVG is sanitized into an opaque-origin sandbox; bounded parsing and decompression, explicit security findings and a URI-scoped controller header exception; later milestone slices remain intentionally tracked in the app repository |
| **`auth-tools`** | Initial local-first v0.1.0 release; dedicated repository | Generate, inspect and verify OTP credentials, and inspect, verify and test WebAuthn/passkey ceremonies locally | HOTP, TOTP and OCRA; strict provisioning URIs; QR, CSV, Google migration and plain PSKC import; bounded CBOR/authenticator-data inspection; assertion verification; an ephemeral browser ceremony lab | OTP material remains memory-only; attestation trust is not claimed; live ceremonies are enabled only at the exact dedicated `auth.toolbox.add-ideas.de` origin (or localhost), while the Portal path remains inspect-only; no raw CTAP or token administration |
## Planned tools