专属域名
文档搜索
轩辕助手
Run助手
邀请有礼
返回顶部
快速返回页面顶部
收起
收起工具栏
轩辕镜像 官方专业版
轩辕镜像 官方专业版轩辕镜像 官方专业版官方专业版
首页个人中心搜索镜像

交易
充值流量我的订单
工具
提交工单镜像收录一键安装
Npm 源Pip 源Homebrew 源
帮助
常见问题
其他
关于我们网站地图

官方QQ群: 1072982923

热门搜索:openclaw🔥nginx🔥redis🔥mysqlopenjdkcursorweb2apimemgraphzabbixetcdubuntucorednsjdk
whisper

viyh/whisper

自动构建
viyh

Whisper provides a simple way to share secret information with someone else.

下载次数: 0状态:自动构建维护者:viyh仓库类型:镜像最近更新:7 小时前
轩辕镜像,快一点,稳很多。点击查看
镜像简介版本下载
轩辕镜像,快一点,稳很多。点击查看

https://github.com/viyh/whisper

Secure secret sharing via one-time or short-lived links.

Share passwords, credentials, keys, or other sensitive data without using insecure channels like email or chat. Secrets are encrypted client-side before transmission -- the server never sees plaintext.

How It Works

  1. Enter secret text or select a file, along with a password.
  2. Choose an expiration: one-time use, 1 hour, 1 day, or 1 week.
  3. Click Create Secret to get a shareable link.
  4. Send the link and password separately (e.g., link via email, password via text).
  5. The recipient opens the link, enters the password, and retrieves the secret.

Security Model

Whisper uses a layered security approach:

  • Client-side encryption: Secrets are encrypted with AES-256-GCM (Web *** API) before leaving the browser. The server never has access to plaintext data.
  • Argon2id password hashing: Passwords are hashed client-side using Argon2id (WASM) before transmission. The server re-hashes with its own Argon2id salt, so even a compromised server cannot recover passwords.
  • One-time secrets: Deleted atomically after retrieval -- concurrent requests cannot both succeed.
  • Rate limiting: 10 attempts per minute per IP, plus per-secret lockout after 10 failed password attempts.
  • Strict CSP: No inline scripts. Content-Security-Policy with explicit allowlists.

See Security Details for the full ***graphic design.

Quick Start

bash
# Generate a config file with a random secret key
export SECRET_KEY=$(head /dev/urandom | LC_ALL=C tr -dc 'A-Za-z0-9' | head -c 48)
sed "s/CHANGE_ME_TO_A_RANDOM_STRING_OF_32_OR_MORE_CHARACTERS/$SECRET_KEY/" src/config.default.yaml > config.yaml

# Build from source (optional, can also pull viyh/whisper:0.2.0):
# docker build -t viyh/whisper .

# Run
docker run -d --name whisper -p 8000:8000 \
    -v $(pwd)/config.yaml:/usr/src/app/config.yaml \
    viyh/whisper:0.2.0

Browse to http://localhost:8000

Configuration

Copy src/config.default.yaml to config.yaml and customize. Mount it into the container at /usr/src/app/config.yaml.

Required Settings

SettingDescription
secret_keyServer-level secret for password hashing. Must be a unique random string of 32+ characters. Change this from the default.
storage_classStorage backend class path (see Storage Backends).

Optional Settings

SettingDefaultDescription
storage_config{}Backend-specific settings (bucket name, path, etc.)
storage_clean_interval900Seconds between expired secret cleanup runs.
max_data_size_kb100Maximum upload size in KB.
app_listen_ip0.0.0.0Internal listen address.
app_port5000Internal Flask port (nginx proxies externally).
app_url_base/URL base path (e.g., /whisper/ for subpath hosting).
argon2_time_cost5Argon2id time cost parameter. Higher = slower + more secure.
argon2_memory_cost131072Argon2id memory cost in KB (*** = 128 MB).
argon2_parallelism1Argon2id parallelism parameter.

Environment Variables

VariableDefaultDescription
WEB_PORT8000External nginx listen port.
LOG_LEVELINFOSet to DEBUG for verbose logging.
CONFIG_FILEconfig.yamlConfig file path inside the container.

Storage Backends

Local Disk (default)

Stores secrets as JSON files. Mount a volume for persistence.

yaml
storage_class: whisper.storage.local.local
storage_config:
    path: /tmp/whisper
bash
docker run -d --name whisper -p 8000:8000 \
    -v $(pwd)/config.yaml:/usr/src/app/config.yaml \
    -v whisper-data:/tmp/whisper \
    whisper

In-Memory

Simplest and most secure -- secrets are lost on restart.

yaml
storage_class: whisper.storage.memory.memory
storage_config: {}

AWS S3

Uses S3 object tags (create_date, expire_date) so the cleanup process only reads tags, not full objects.

yaml
storage_class: whisper.storage.aws.s3
storage_config:
    bucket_name: my-whisper-bucket
    bucket_path: secrets

Credentials: IAM role (recommended), credential file mount (-v ~/.aws:/.aws:ro), or environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_DEFAULT_REGION).

Minimum IAM permissions:

json
{
    "Version": "2012-10-17",
    "Statement": [{
        "Effect": "Allow",
        "Action": [
            "s3:ListBucket", "s3:GetBucketLocation",
            "s3:GetObject", "s3:PutObject", "s3:DeleteObject",
            "s3:GetObjectTagging", "s3:PutObjectTagging", "s3:DeleteObjectTagging"
        ],
        "Resource": [
            "arn:aws:s3:::my-whisper-bucket",
            "arn:aws:s3:::my-whisper-bucket/*"
        ]
    }]
}

GCP Cloud Storage

Uses object metadata (create_date, expire_date) for efficient cleanup.

yaml
storage_class: whisper.storage.gcp.gcs
storage_config:
    gcp_project: my-project
    bucket_name: my-whisper-bucket
    bucket_path: secrets

Credentials: Application default credentials (recommended), or mount gcloud config (-v ~/.config/gcloud:/.config/gcloud:ro).

Required GCS permissions:

storage.objects.get, storage.objects.update, storage.objects.list,
storage.objects.create, storage.objects.delete,
storage.multipartUploads.create, storage.multipartUploads.abort,
storage.multipartUploads.listParts, storage.multipartUploads.list,
storage.buckets.get

Or use built-in roles: roles/storage.legacyObjectOwner + roles/storage.legacyBucketWriter.

Security Details

Secret Structure

json
{
    "id": "8d692508856cabba82d73e15ef6f0364de70546c",
    "create_date": 1657421435,
    "expire_date": -1,
    "data": "U2FsdGVkX1/qMytBOYisCGZ3KjpkowinHQhu12lGY8E=",
    "hash": "$argon2id$v=19$m=131072,t=5,p=1$...",
    "version": 2
}
FieldDescription
id160-bit random hex identifier (40 chars).
create_dateUNIX timestamp of creation.
expire_dateUNIX timestamp of expiration, or -1 for one-time use.
dataClient-encrypted ciphertext (AES-256-GCM for v2, AES-CBC for v1).
hashServer-side password hash (Argon2id for v2, bcrypt for v1).
version*** version: 1 = legacy, 2 = current.

***graphic Flow (v2)

Creating a secret:

  1. User enters plaintext + password.
  2. Client hashes password with Argon2id (configurable params, public salt from URL origin).
  3. Client encrypts plaintext with AES-256-GCM via Web *** API (random 96-bit IV, PBKDF2-derived key at 210,000 iterations).
  4. Client sends encrypted data + Argon2id hash to server.
  5. Server re-hashes with Argon2id using server secret_key as additional input.
  6. Server stores encrypted data + server-side hash.

Retrieving a secret:

  1. Client hashes password with Argon2id (same params).
  2. Server verifies against stored hash.
  3. For one-time secrets: atomic claim-and-delete before returning data.
  4. Client decrypts with AES-256-GCM using original password.

The server never has access to the plaintext password or data.

Legacy v1 Secrets

If you have a pre-0.2.0 secret link that was created with the v1 format (PBKDF2 + bcrypt + ***JS AES-CBC), check out the release/0.1.0_to_0.2.0 branch, which retains v1 decryption support.

Rate Limiting

The default in-memory rate limiter (storage_uri="memory://") tracks state per-gunicorn-worker. In multi-worker or multi-container deployments, each worker enforces limits independently. For shared rate-limit state across workers, configure a Redis backend via flask-limiter.

Development

Writing Storage Backends

Storage backends must subclass store and implement:

MethodDescription
start()Initialize the backend.
get_secret(secret_id)Return secret object or False.
set_secret(s)Save a secret object.
delete_secret(secret_id)Delete a secret.
claim_secret(secret_id)Atomically delete and return True if it existed (for one-time secrets).
delete_expired()Iterate stored secrets and delete any where is_expired() returns True.

See src/whisper/storage/memory.py for a minimal example.

Running for Development

bash
docker build -t whisper:dev .
docker run -it --rm --name whisper -p 8000:8000 \
    -e LOG_LEVEL=DEBUG \
    -v $(pwd)/src/config.yaml:/usr/src/app/config.yaml \
    whisper:dev

Building

bash
# Standard build
docker build -t whisper:0.2.0 .

# Cross-platform build
docker buildx build --platform=linux/amd64,linux/arm64 \
    -t whisper:0.2.0 .

Tech Stack

Backend: Python 3.12, Flask 3.1, Gunicorn 23, Nginx (Debian Slim)

**Client-side *****: Web *** API (AES-256-GCM, PBKDF2), argon2-browser (WASM)

Frontend: Bootstrap 5.3, clipboard.js, vanilla JS (no jQuery)

Storage: Local disk, in-memory, AWS S3, GCP Cloud Storage

Contributing

Pull requests are welcome. See CONTRIBUTING.md for setup and guidelines. For security issues, see SECURITY.md.

Author

Joe Richards (GitHub: https://github.com/viyh)

License

MIT License

查看更多 whisper 相关镜像 →

openeuler/whisper logo

openeuler/whisper

openeuler
暂无描述
3 次收藏1.5千+ 次下载
7 个月前更新
nosana/whisper logo

nosana/whisper

nosana
暂无描述
50万+ 次下载
1 年前更新
dustynv/whisper logo

dustynv/whisper

dustynv
用于Jetson平台的Whisper音频转录Jupyter环境,包含原始notebooks及额外录音转录notebook,自动启动Jupyter Lab(HTTPS访问,密码nvidia),支持交互式语音识别与音频处理任务。
4.1千+ 次下载
2 年前更新

轩辕镜像配置手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

Docker 配置

登录仓库拉取

通过 Docker 登录认证访问私有仓库

专属域名拉取

无需登录使用专属域名

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

Harbor 镜像源配置

Harbor Proxy Repository 对接专属域名

Portainer 镜像源配置

Portainer Registries 加速拉取

Nexus 镜像源配置

Nexus3 Docker Proxy 内网缓存

系统配置

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

MacOS OrbStack

MacOS OrbStack 容器配置

Docker Compose

Docker Compose 项目配置

NAS 设备

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

极空间

极空间 NAS 系统配置服务

网络设备

爱快路由

爱快 iKuai 路由系统配置

宝塔面板

在宝塔面板一键配置镜像

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

使用与功能问题

配置了专属域名后,docker search 为什么会报错?

docker search 限制

Docker Hub 上有的镜像,为什么在轩辕镜像网站搜不到?

站内搜不到镜像

机器不能直连外网时,怎么用 docker save / load 迁镜像?

离线 save/load

docker pull 拉插件报错(plugin v1+json)怎么办?

插件要用 plugin install

WSL 里 Docker 拉镜像特别慢,怎么排查和优化?

WSL 拉取慢

轩辕镜像安全吗?如何用 digest 校验镜像没被篡改?

安全与 digest

第一次用轩辕镜像拉 Docker 镜像,要怎么登录和配置?

新手拉取配置

错误码与失败问题

docker pull 提示 manifest unknown 怎么办?

manifest unknown

docker pull 提示 no matching manifest 怎么办?

no matching manifest(架构)

镜像已拉取完成,却提示 invalid tar header 或 failed to register layer 怎么办?

invalid tar header(解压)

Docker pull 时 HTTPS / TLS 证书验证失败怎么办?

TLS 证书失败

Docker pull 时 DNS 解析超时或连不上仓库怎么办?

DNS 超时

Docker 拉取出现 410 Gone 怎么办?

410 Gone 排查

出现 402 或「流量用尽」提示怎么办?

402 与流量用尽

Docker 拉取提示 UNAUTHORIZED(401)怎么办?

401 认证失败

遇到 429 Too Many Requests(请求太频繁)怎么办?

429 限流

docker login 提示 Cannot autolaunch D-Bus,还算登录成功吗?

D-Bus 凭证提示

为什么会出现「单层超过 20GB」或 413,无法加速拉取?

413 与超大单层

账号 / 计费 / 权限

轩辕镜像免费版和专业版有什么区别?

免费版与专业版区别

轩辕镜像支持哪些 Docker 镜像仓库?

支持的镜像仓库

镜像拉取失败还会不会扣流量?

失败是否计费

麒麟 V10 / 统信 UOS 提示 KYSEC 权限不够怎么办?

KYSEC 拦截脚本

如何在轩辕镜像申请开具发票?

申请开票

怎么修改轩辕镜像的网站登录和仓库登录密码?

修改登录密码

如何注销轩辕镜像账户?要注意什么?

注销账户

配置与原理类

写了 registry-mirrors,为什么还是走官方或仍然报错?

mirrors 不生效

怎么用 docker tag 去掉镜像名里的轩辕域名前缀?

去掉域名前缀

如何拉取指定 CPU 架构的镜像(如 ARM64、AMD64)?

指定架构拉取

用轩辕镜像拉镜像时快时慢,常见原因有哪些?

拉取速度原因

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
viyh/whisper
博客公告Docker 镜像公告与技术博客
热门镜像查看热门 Docker 镜像推荐
一键安装一键安装 Docker 并配置镜像源
镜像拉取问题咨询请 提交工单,官方技术交流群:1072982923。轩辕镜像所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
镜像拉取问题咨询请提交工单,官方技术交流群:。轩辕镜像所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
商务合作:点击复制邮箱
©2024-2026 源码跳动
商务合作:点击复制邮箱Copyright © 2024-2026 杭州源码跳动科技有限公司. All rights reserved.