おもしろバグ
keepassxc#13825
43 views
FYI KeePassXC now has native Windows Arm64 builds as of v2.8.0 \o/
github.com/keepassxreboot/keepassxc/releases/tag/…
#MVPBuzz
2 likes · 1 repost · 288 views
KeePassXC 2.8.0で入ったリモート動機機能を試してみようかと思ったら設定画面に見当たらない?
メニューの「データベース」->「リモート同期」->「リモート同期をセットアップ」
で生えてくる
同期コマンドはどうしょうかな……そろそろ労働にいかねばなのでまた後ほど
Issues · keepassxreboot/keepassxc github.com/keepassxreboot/keepassxc/issues
デカくね 遊んでみるかぁ
github.com/keepassxreboot/keepassxc/releases/tag/…
8 views
密码别再散在便签和表格里。🔐
KeePassXC 把账号信息存在本地加密密码库，还带密码生成器和浏览器集成。记得备份库文件。🗝️
keepassxreboot/keepassxc
#PasswordManager #Privacy #浇朋友 #蓝朋友 #互关 #fo
1 like · 42 views
KeePassXC GitHub Explained: Local Encryption and Secure Browser IPC
keepassxc by keepassxreboot: keepassxreboot/keepassxc
KeePassXC is presented as a local-first password manager whose security model keeps the encrypted vault and credential transport on the user's own machine. This architecture overview explains the trade-off behind omitting native cloud synchronization, then follows a KDBX 4.0 database through its compressed and encrypted layers. It covers AES-256 or ChaCha20 at rest, Argon2id's memory-hard key derivation against GPU-focused guessing, and native C++ memory handling when a database is locked.
The second half focuses on browser integration. Native Messaging, a local proxy, Unix domain sockets, and an authenticated session connect the vault to the browser while treating the host operating system as part of the threat model. The overview also covers passkey certificate checks, sandbox boundaries that can block IPC, atomic-save conflicts on cloud-synced files, and the manual synchronization and configuration responsibilities that come with a local-first design.
TimeStamps:
0:00 Offline storage and data sovereignty
0:49 Why browser access becomes a transport problem
1:58 KDBX 4.0 layers and encryption at rest
2:29 Argon2id and memory-hard key derivation
3:41 Native C++ memory handling
4:48 Native Messaging and local IPC
5:30 Encrypted browser sessions and passkeys
6:37 Sandbox boundaries and atomic-save friction
7:40 The end-to-end credential pipeline
8:08 Local-first limitations and operator responsibility
8:29 Repository guidance and ongoing discipline
🔐 Local-first KDBX storage and Argon2id protection
🌐 Native Messaging bridges the vault and browser
🧠 Native C++ memory handling and secure deletion on lock
⚠️ Sandboxing, sync conflicts, and manual orchestration trade-offs
KeePassXC's core trade-off is clear: the vault and browser bridge stay local, but synchronization and host configuration remain the operator's responsibility. For security-conscious desktop users, the useful questions are whether KDBX encryption, Argon2id, native messaging, and local-first workflows fit their threat model—and whether they can manage the resulting operational friction.
#KeePassXC #PasswordSecurity #OpenSource
[de-DE] YNAS ynp_192239ad2ab466ec Kinofilm
Privater automatisierter Staging-Upload. Paketidentität: ynp_192239ad2ab466ec; Ausgabe: cinematic.
[es-US] YNAS ynp_192239ad2ab466ec cinemática
Carga de entorno de prueba de automatización privada. Identidad del paquete: ynp_192239ad2ab466ec; salida: cinematográfica.
[fr-FR] YNAS ynp_192239ad2ab466ec cinématique
Téléchargement de l'environnement de test d'automatisation privé. Identifiant du package : ynp_192239ad2ab466ec ; sortie : cinématique.
[hi] YNAS ynp_192239ad2ab466ec सिनेमैटिक
निजी स्वचालन स्टेजिंग अपलोड। पैकेज पहचान: ynp_192239ad2ab466ec; आउटपुट: सिनेमाई।
[id] YNAS ynp_192239ad2ab466ec sinematik
Unggahan staging otomatisasi pribadi. Identitas paket: ynp_192239ad2ab466ec; output: cinematic.
[it] YNAS ynp_192239ad2ab466ec cinematic
Caricamento di automazione privata. Identità del pacchetto: ynp_192239ad2ab466ec; output: cinematico.
[pt-BR] YNAS ynp_192239ad2ab466ec cinematográfico
Upload de teste de automação privada. Identificação do pacote: ynp_192239ad2ab466ec; saída: cinemática.
3 likes · 843 views
RP
KeePass系でちょっと気になるのが、Passkeyの秘密鍵がハード的にセキュアな領域（TPMとか）ではなく暗号化されてはいるものの普通の領域にあるkdbxファイルに保存されるっぽいあたりかねえ。
実装は色々あるけど多分共通してる。
KeePassDX#2274
keepassxc#11264
必要十分と言われればまあそうなんだけど、パスキーについてはそれぞれローカルで管理するか、利便性重視ならGoogleに投げるかな……
I hate passkeys. They're bound to a single device, and I have like 5.
The only case where it works well is with my work PC, where I have only 1 work PC. I think the main problem with passkeys is that it treats users as stupid. At the end of the day, whatever cryptographic value is used, needs to be managed by the user in some way, but passkeys explicitly disallow that. There were those shenanigans disallowing keepassxc#10407
1 point
密码一多我就开始乱。。。
KeePassXC 是桌面端开源密码库。Windows、Mac、Linux 都能装，密码和一次性验证码加密塞进本地一个文件里。
最新稳定版 2.7.12。我最在意的是那个文件叫 KDBX，备份和同步都你自己定，不强制上云。
GitHub 约 2.9 万星，GPL-2/3
keepassxreboot/keepassxc t.co
1 like · 40 views
keepassxc#10407
> To be very honest here, you risk having KeePassXC blocked by relying parties
This threat, because someone dared to give users control, is completely unacceptable to me.
Mentions
おもしろバグ keepassxc#13825
FYI KeePassXC now has native Windows Arm64 builds as of v2.8.0 \o/ github.com/keepassxreboot/keepassxc/releases/tag/… #MVPBuzz
KeePassXC 2.8.0で入ったリモート動機機能を試してみようかと思ったら設定画面に見当たらない? メニューの「データベース」->「リモート同期」->「リモート同期をセットアップ」 で生えてくる 同期コマンドはどうしょうかな……そろそろ労働にいかねばなのでまた後ほど Issues · keepassxreboot/keepassxc github.com/keepassxreboot/keepassxc/issues
デカくね 遊んでみるかぁ github.com/keepassxreboot/keepassxc/releases/tag/…
密码别再散在便签和表格里。🔐 KeePassXC 把账号信息存在本地加密密码库，还带密码生成器和浏览器集成。记得备份库文件。🗝️ keepassxreboot/keepassxc #PasswordManager #Privacy #浇朋友 #蓝朋友 #互关 #fo
KeePassXC GitHub Explained: Local Encryption and Secure Browser IPC keepassxc by keepassxreboot: keepassxreboot/keepassxc KeePassXC is presented as a local-first password manager whose security model keeps the encrypted vault and credential transport on the user's own machine. This architecture overview explains the trade-off behind omitting native cloud synchronization, then follows a KDBX 4.0 database through its compressed and encrypted layers. It covers AES-256 or ChaCha20 at rest, Argon2id's memory-hard key derivation against GPU-focused guessing, and native C++ memory handling when a database is locked. The second half focuses on browser integration. Native Messaging, a local proxy, Unix domain sockets, and an authenticated session connect the vault to the browser while treating the host operating system as part of the threat model. The overview also covers passkey certificate checks, sandbox boundaries that can block IPC, atomic-save conflicts on cloud-synced files, and the manual synchronization and configuration responsibilities that come with a local-first design. TimeStamps: 0:00 Offline storage and data sovereignty 0:49 Why browser access becomes a transport problem 1:58 KDBX 4.0 layers and encryption at rest 2:29 Argon2id and memory-hard key derivation 3:41 Native C++ memory handling 4:48 Native Messaging and local IPC 5:30 Encrypted browser sessions and passkeys 6:37 Sandbox boundaries and atomic-save friction 7:40 The end-to-end credential pipeline 8:08 Local-first limitations and operator responsibility 8:29 Repository guidance and ongoing discipline 🔐 Local-first KDBX storage and Argon2id protection 🌐 Native Messaging bridges the vault and browser 🧠 Native C++ memory handling and secure deletion on lock ⚠️ Sandboxing, sync conflicts, and manual orchestration trade-offs KeePassXC's core trade-off is clear: the vault and browser bridge stay local, but synchronization and host configuration remain the operator's responsibility. For security-conscious desktop users, the useful questions are whether KDBX encryption, Argon2id, native messaging, and local-first workflows fit their threat model—and whether they can manage the resulting operational friction. #KeePassXC #PasswordSecurity #OpenSource [de-DE] YNAS ynp_192239ad2ab466ec Kinofilm Privater automatisierter Staging-Upload. Paketidentität: ynp_192239ad2ab466ec; Ausgabe: cinematic. [es-US] YNAS ynp_192239ad2ab466ec cinemática Carga de entorno de prueba de automatización privada. Identidad del paquete: ynp_192239ad2ab466ec; salida: cinematográfica. [fr-FR] YNAS ynp_192239ad2ab466ec cinématique Téléchargement de l'environnement de test d'automatisation privé. Identifiant du package : ynp_192239ad2ab466ec ; sortie : cinématique. [hi] YNAS ynp_192239ad2ab466ec सिनेमैटिक निजी स्वचालन स्टेजिंग अपलोड। पैकेज पहचान: ynp_192239ad2ab466ec; आउटपुट: सिनेमाई। [id] YNAS ynp_192239ad2ab466ec sinematik Unggahan staging otomatisasi pribadi. Identitas paket: ynp_192239ad2ab466ec; output: cinematic. [it] YNAS ynp_192239ad2ab466ec cinematic Caricamento di automazione privata. Identità del pacchetto: ynp_192239ad2ab466ec; output: cinematico. [pt-BR] YNAS ynp_192239ad2ab466ec cinematográfico Upload de teste de automação privada. Identificação do pacote: ynp_192239ad2ab466ec; saída: cinemática.
RP KeePass系でちょっと気になるのが、Passkeyの秘密鍵がハード的にセキュアな領域（TPMとか）ではなく暗号化されてはいるものの普通の領域にあるkdbxファイルに保存されるっぽいあたりかねえ。 実装は色々あるけど多分共通してる。 KeePassDX#2274 keepassxc#11264 必要十分と言われればまあそうなんだけど、パスキーについてはそれぞれローカルで管理するか、利便性重視ならGoogleに投げるかな……
I hate passkeys. They're bound to a single device, and I have like 5. The only case where it works well is with my work PC, where I have only 1 work PC. I think the main problem with passkeys is that it treats users as stupid. At the end of the day, whatever cryptographic value is used, needs to be managed by the user in some way, but passkeys explicitly disallow that. There were those shenanigans disallowing keepassxc#10407
密码一多我就开始乱。。。 KeePassXC 是桌面端开源密码库。Windows、Mac、Linux 都能装，密码和一次性验证码加密塞进本地一个文件里。 最新稳定版 2.7.12。我最在意的是那个文件叫 KDBX，备份和同步都你自己定，不强制上云。 GitHub 约 2.9 万星，GPL-2/3 keepassxreboot/keepassxc t.co
keepassxc#10407 > To be very honest here, you risk having KeePassXC blocked by relying parties This threat, because someone dared to give users control, is completely unacceptable to me.