[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3gbsy346zntpt":3},{"code":4,"message":5,"data":6,"timestamp":73},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":46,"summary_md":47,"topic":48,"github_topics":51,"license":63,"homepage":64,"updated_at":65,"history":66},"keepassxreboot\u002Fkeepassxc",9,"KeePassXC is a cross-platform community-driven port of the Windows application “KeePass Password Safe”.","C++",29464,1975,33,3891,[16,22,28,34,40],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},35859877,"KeePassXC pull request to add basic support for WebAuthn",343,199,"2023-05-08",{"id":23,"title":24,"points":25,"comments":26,"posted_at":27},39698502,"KeePassXC Issue: [Passkeys] should never be exported in clear text",34,19,"2024-03-13",{"id":29,"title":30,"points":31,"comments":32,"posted_at":33},40319031,"Debian Sid No-Feature KeePassXC Package",18,5,"2024-05-10",{"id":35,"title":36,"points":37,"comments":38,"posted_at":39},40400775,"Debian removes KeePassXC browser integration",10,2,"2024-05-18",{"id":41,"title":42,"points":43,"comments":44,"posted_at":45},29723703,"KeePassXC",4,0,"2021-12-29","给想把密码库当作本地加密文件、而不是云账号的人使用的离线 KeePass 兼容密码管理器。","KeePassXC 适合那些希望密码库就是自己手里一个文件、而不是托管账号的人。它成熟、跨平台，刻意保持本地优先；代价是同步、备份和浏览器集成这些事要自己负责。\n\n## 解决什么问题\n你想把密码、TOTP 验证码、笔记、附件和 SSH 密钥放在一个加密位置，并在自己用的多台机器上打开。用云密码管理器时，服务商替你保管密码库，你得接受它的账号、同步和导出规则。KeePassXC 把这件事换成一个由你选定路径的 KDBX 文件，静态加密，可在 Windows、macOS 和 Linux 上使用，也能打开 KeePass 兼容数据库。最后你拿到的是可以备份、可以搬走的文件，但没有服务商替你打理。\n\n## 有什么不同\n项目的核心取向是互操作，而不是自建云服务。支持 KDBX4 和 KDBX3，意味着同一份文件还能被其他 KeePass 兼容工具打开；浏览器集成覆盖 Chrome、Firefox、Edge、Chromium、Vivaldi、Brave 和 Tor-Browser，负责日常登录填充；基于浏览器集成的 passkey 支持则把密码库往 WebAuthn 凭据方向延伸。YubiKey\u002FOnlyKey challenge-response、Auto-Type、CLI 和 SSH Agent 集成让它不只是表单填充器，CSV、1Password、Bitwarden、Proton Pass 等导入方式也降低了迁移成本。\n\n代价是这些能力围绕文件拼装，而不是以服务形式提供。浏览器支持依赖扩展和 native messaging 的配置，发行版打的包也未必包含全部功能。2024-05-18 一条关于 Debian 打包的 Hacker News 评论中，用户 crtasm 指出当时讨论的是不含某些功能的打包变体，而浏览器集成仍可通过其他途径获得，因此包来源很关键。2023-05-08 关于加入基础 WebAuthn 支持的讨论帖有 199 条评论；用户 account-5 把这项工作描述为通往不绑定设备、不绑定厂商的 passkey 的第一步，回复中也提醒 attestation 和依赖方行为仍会影响实际可用性。\n\n## 谁值得试\n比较适合已经用自选云盘同步文件、希望密码库能和其他 KeePass 兼容工具共用，并且看重 Auto-Type、TOTP 和硬件密钥解锁的开发者或注重隐私的用户。不太适合希望开箱即用同步、家庭共享和由厂商处理账号恢复的人：这些在这里会变成文件管理和扩展配置工作，而主密码或文件所有副本丢失后，项目无法替你恢复。\n\n## 使用条件与边界\n开始使用需要一个数据库文件、主密码或密钥文件，以及兼容客户端；预编译二进制和发行版包可参考[快速开始指南](https:\u002F\u002Fkeepassxc.org\u002Fdocs\u002FKeePassXC_GettingStarted.html)，详细说明在[用户指南](https:\u002F\u002Fkeepassxc.org\u002Fdocs\u002FKeePassXC_UserGuide.html)。自动填充和 passkey 依赖浏览器集成已安装并配对；Debian 打包讨论也说明发行版构建可能与上游不同，应先确认自己的包包含什么。\n\n日常维护要自己承担：做好备份版本管理、谨慎同步以避免冲突副本、保护好主凭据，并在更新后确认扩展版本。项目提供构建说明，但不提供托管服务，也不为主密码遗忘提供恢复路径。\n\n## HotRepo 点评\nHotRepo 记录到两次登上每日榜，分别是 2026-10-24（+32 星）和 2026-10-25（+33 星），当时约 29,460 星。样本太短，无法判断趋势能否持续；但如果目标就是本地文件，这个长期项目仍是稳妥选择。用前请确认你所用发行版的包是否包含浏览器集成和所需的硬件密钥支持。",{"slug":49,"name":50},"security","安全",[52,53,54,55,56,57,58,59,60,49,61,62],"cross-platform","hacktoberfest","keepass","keepassxc","linux","macos","password","password-manager","privacy","windows","yubikey","NOASSERTION","https:\u002F\u002Fkeepassxc.org\u002F","2026-10-25T03:12:15Z",[67,71],{"date":68,"stars":69,"stars_gained":70},"2026-10-24",29455,32,{"date":72,"stars":11,"stars_gained":13},"2026-10-25",1792921647]