Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Optional encryption of Sentient's data with a key you hold

未关闭
#112 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
python

调研方向

Read ADR 0003 and ADR 0005, then inspect sentient/store/, sentient/secrets, and docs/PRIVACY.md to understand storage and key handling. Check how FTS5 and sqlite-vec are loaded. Done means disk data is unreadable without the key when encryption is enabled, existing behavior still works, and migration in both directions is tested.

由索引模型根据 Issue 内容生成。

描述

area: engine enhancement help wanted

Meta's "Confidential VM" for Muse encrypts the agent's data with a key only the user holds. Sentient keeps everything on your own disk, but ~/.sentient is not encrypted at rest.

Idea: an optional setting that encrypts the SQLite database and the files folder with a key kept in the operating system's keychain, or derived from a passphrase you type at start-up. Off by default. Turning it on migrates existing data.

Inspired by: https://tech-insider.org/meta-muse-personal-ai-agent-launch-2026/

Where: sentient/store/ (for example SQLCipher; check that FTS5 and sqlite-vec still load), sentient/secrets for the key, and docs/PRIVACY.md. This builds on ADR 0003 (one SQLite file) and ADR 0005 (keychain), so please add a new ADR.

Done when: with the setting on, the files on disk are unreadable without the key, everything works as before, and migration both ways is tested.

主要语言
Python
星标
702
派生
113
平均合并
5 小时 8 分钟
30 天内合并 PR
171

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

existence-master/Sentient 的其他 Issue

查看 existence-master/Sentient 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。