PRISMA_FIELD_DECRYPTION_KEYS is never set, so the AES key cannot be rotated
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 57/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- helm, typescript
调研方向
Start with .helm/ctrl/templates/backend/deployment.yaml and cron.yaml, where PRISMA_FIELD_ENCRYPTION_KEY is currently set; then check how the application and prisma-field-encryption read environment variables. Configure retired decryption keys through PRISMA_FIELD_DECRYPTION_KEYS while preserving the current key setup. Done when both deployments can load the retired keys needed for gradual rotation and restoring backups.
由索引模型根据 Issue 内容生成。
描述
We have no way to hold more than one encryption key at a time. PRISMA_FIELD_ENCRYPTION_KEY is set in .helm/ctrl/templates/backend/deployment.yaml and cron.yaml, and that single key is all the app ever sees.
prisma-field-encryption does support more. It takes a current encryption key plus a list of retired decryption keys via PRISMA_FIELD_DECRYPTION_KEYS, and every encrypted value already carries a fingerprint of the key that wrote it, so reads can pick the right one per row. We just never configure the list.
Two things depend on that:
- Rotation. Changing the key means decrypting everything under the old one and re-encrypting under the new one. With only one key loaded, there's no window where both are available, so it can't be done gradually.
- Old backups. A backup stays tied to whichever key was current when it was taken. Restoring one and reading the encrypted columns needs that key, whether or not we've rotated since.
So retired keys would need to outlive the backups that depend on them, and right now there's no mechanism to load them even if we kept them somewhere.
- 主要语言
- TypeScript
- 星标
- 4
- 派生
- 0
- 平均合并
- 14 小时 50 分钟
- 30 天内合并 PR
- 5
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Garvan-Data-Science-Platform/ctrl 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 82/100
-
admin-client backend bug
难度 2/5 1-3 小时 新手友好度 76/100
-
backend bug
难度 2/5 1-3 小时 新手友好度 68/100
Garvan-Data-Science-Platform/ctrl#970 · 1 条评论 ·
-
backend bug
难度 2/5 1-3 小时 新手友好度 72/100
-
backend bug
难度 2/5 1-3 小时 新手友好度 78/100
查看 Garvan-Data-Science-Platform/ctrl 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
AvaProtocol/ava-sdk-js#276 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
apollographql/apollo-client#13493 ·
维护者通常 1 天内回复
-
Custom hosts written as trailing-dot FQDNs (`host.local.`) aren't detected as local backends可能已有人在做 @roboomp 今天认领。 未关闭bug prio:p2 providers triaged
难度 2/5 1-3 小时 新手友好度 82/100
can1357/oh-my-pi#15798 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
code-yeongyu/oh-my-openagent#10172 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
PDFCraftTool/pdfcraft#189 ·