Name of the Script
Yopass
Script Type
CT (LXC Container)
Does this script support arm64?
arm64 supported
📋 Script Details
Yopass shares secrets through one-time links. The payload is encrypted in the browser, so the server only stores an opaque blob with a TTL, and the key travels in the URL fragment which never reaches the server. Requested in discussion #3097.
- Two builds, taken from the upstream Dockerfile:
go build ./cmd/yopass-server for the binary, and yarn install && yarn build in website/ for the frontend. The frontend is not embedded — go:embed appears only in pkg/server/license.go — so the server is started with --asset-path /opt/yopass/website/dist.
- Redis as backend rather than the default memcached: one less moving part, and it matches what other scripts here already use.
--database redis --redis redis://127.0.0.1:6379/0.
--address 0.0.0.0 is explicit; the flag defaults to empty.
- Note: this belongs behind TLS. Encryption happens in the browser and a non-secure context undermines the entire premise — flagged as the first warning in the JSON.
- Redis persistence is deliberately not configured: a restart dropping pending secrets is the desired behaviour for a one-time-secret service.
Source: https://github.com/jhaals/yopass
Name of the Script
Yopass
Script Type
CT (LXC Container)
Does this script support arm64?
arm64 supported
📋 Script Details
Yopass shares secrets through one-time links. The payload is encrypted in the browser, so the server only stores an opaque blob with a TTL, and the key travels in the URL fragment which never reaches the server. Requested in discussion #3097.
go build ./cmd/yopass-serverfor the binary, andyarn install && yarn buildinwebsite/for the frontend. The frontend is not embedded —go:embedappears only inpkg/server/license.go— so the server is started with--asset-path /opt/yopass/website/dist.--database redis --redis redis://127.0.0.1:6379/0.--address 0.0.0.0is explicit; the flag defaults to empty.Source: https://github.com/jhaals/yopass