Skip to content

Airlock v0.1.5

Choose a tag to compare

View all tags
@LouisonH LouisonH released this 01 Aug 15:58
· 25 commits to main since this release
v0.1.5
0f1bfb7

Airlock v0.1.5 - Interactive Shell and Cross-Platform Bootstrap Release

Released: August 1, 2026

English | 简体中文 | 日本語

Added

  • Optional per-route interactive SSH shells, disabled by default. Setting
    allow_interactive_shell: true (which requires allow_all_commands: true)
    lets PuTTY and ssh clients enter the upstream shell while Airlock still
    injects the stored upstream credentials. PTY metadata is forwarded only
    while the switch is enabled.
  • Plain shell requests on non-interactive routes now receive actionable
    guidance instead of a refused shell, and single-command routes run their
    exact command when a shell is requested.
  • Protected keyword egress rewrites for SSH commands.
  • Explicit per-route SFTP permission, disabled by default, for modern
    scp/SFTP clients.
  • Windows x64/x86/arm64 and Linux x64/arm64/ARMv7 Core and CLI
    cross-compilation with owner-only Windows named-pipe control, Credential
    Manager / Secret Service backends, Linux native prompts, and CI preview
    installer contracts that fail closed. Windows preview installers are
    attached to this release for manual testing and remain unsigned preview
    artifacts rather than public checksummed installers.

Fixed

  • Interactive-shell PTY dimensions were forwarded transposed, causing garbled
    input display in terminals; the upstream session now receives the client's
    actual rows and columns.

Verification

  • Airlock_0.1.5_aarch64.dmg
  • Airlock_0.1.5_aarch64.app.zip
  • SHA256SUMS-v0.1.5.txt
e404c805c8c410012eca0996158c0d69f48f107c4cd81f677c2391e37f3f59c3  Airlock_0.1.5_aarch64.dmg
9441efd974e0bff7a8ae92fe1fb5e255ed59e2548740a34564bfee0ea8aa60af  Airlock_0.1.5_aarch64.app.zip

go vet ./...
go test -race ./...

Release boundary

This is still a macOS Apple Silicon technical preview. The production-readiness
audit from v0.1.4 applies; it is not an independent third-party
certification. The application remains ad-hoc signed and not Apple-notarized.
Use the Keychain Strict profile for same-user hostile-process resistance, keep
LAN ingress private, and use a least-privilege upstream SSH account.

See the security policy,
installation guide, and
changelog.

Assets 6
Loading