[Feature]: make self-destruction PIN less noticeable to an adversary
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The issue names no files, tests, or entry points. Start by comparing the regular and self-destruction PIN flows using the linked video, then review issue #4765 for the proposed decoy-account direction; done should make the two PIN outcomes indistinguishable to an adversary without breaking data destruction.
由索引模型根据 Issue 内容生成。
描述
Is there an existing issue for this?
- I have searched the existing issues
Platform
Android
App version
6.5.6
Feature
The data destruction password works correctly, but an adversary can see with the naked eye whether the user entered the regular password or the self-destruction password. In some cases, the user may be put in danger if the adversary notices that they are hiding something. The video below compares the app’s behavior when the user enters the correct password and when they enter the self-destruction password:
https://youtube.com/shorts/AH-mBpOPC6U?si=FM9eO1UX1f8arBeh
First, the application loads instantly when the regular PIN is entered, but it takes several seconds to load when the user enters the duress PIN. A possible solution would be to add a delay to regular PIN verification, for example by using a key derivation function, so that entering the PIN takes roughly the same amount of time in both scenarios.
Second, when the regular PIN is entered, the size of the user data remains the same before and after unlocking the app. However, when the decoy PIN is entered, the size of the user data decreases after the app is unlocked. Moreover, if the user previously had several megabytes of user data and then shows the adversary an empty account, this may be enough for the adversary to conclude that the user has destroyed their data.
This issue is harder to solve. One possible mitigation would be to preallocate some space even for empty accounts, or to show a decoy user account instead of an empty one after the self-destruction password is entered, as proposed here.
- 主要语言
- Haskell
- 星标
- 19.5k
- 派生
- 1.4k
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 117
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
simplex-chat/simplex-chat 的其他 Issue
-
bug triage
难度 2/5 1-3 小时 新手友好度 68/100
simplex-chat/simplex-chat#7649 ·
维护者通常 1 天内回复
-
enhancement triage
难度 2/5 1-3 小时 新手友好度 72/100
simplex-chat/simplex-chat#7585 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
simplex-chat/simplex-chat#7248 ·
维护者通常 1 天内回复
-
Dead link at /docs/guide/readme.html可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 1/5 1 小时以内 新手友好度 75/100
simplex-chat/simplex-chat#6782 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
simplex-chat/simplex-chat#6772 ·
维护者通常 1 天内回复
查看 simplex-chat/simplex-chat 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
puffnfresh/haskell-jwt#12 ·
-
cabal update underdocumented可能已有人在做 @KeuqS 于 1 天前认领。 未关闭attention: pr-welcome documentation good first issue
难度 1/5 1 小时以内 新手友好度 67/100
维护者通常 1 天内回复
-
LaTeX writer: definition term containing `=` breaks the build when `pdfstandard` is set可能已有人在做 @enieuwy 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
status: needs triage type: enhancement
难度 1/5 1 小时以内 新手友好度 90/100
haskell/haskell-language-server#5128 ·
维护者通常 1 天内回复