Force an immediate BSOD + system reset/shutdown after "Clear encryption keys from memory if a new device is inserted" is triggered
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- c
调研方向
The issue identifies the DBT_DEVICEARRIVAL path and VC_IOCTL_EMERGENCY_CLEAR_ALL_KEYS; start by locating that handler and the key-clearing call. Review how the driver handles emergency key clearing and system crash or reset behavior. Done means the requested immediate crash followed by reset or shutdown occurs after keys are wiped, including when Windows automatic reboot is disabled.
由索引模型根据 Issue 内容生成。
描述
Currently
The documentation (doc/html/en/VeraCrypt RAM Encryption.html) states:
If a new device is inserted, master keys are immediately purged from memory, resulting in a Windows BSOD.
However, when DBT_DEVICEARRIVAL triggers VC_IOCTL_EMERGENCY_CLEAR_ALL_KEYS, VeraCrypt only wipes the encryption keys from RAM and calls WipeCache(). It does not actively force a BSOD or system reset, passively relying on Windows to eventually crash with BSOD when a critical kernel disk I/O request fails.
During practical testing on Windows 10 (32GB RAM), inserting a new USB drive while on the Win+L lock screen successfully triggered key clearing (files on the system drive could no longer be opened), but in ~1/15 tests Windows somehow did not BSOD. Because the OS session, file explorer, thumbnails, folder names, and USB drivers were already cached in RAM, Windows allowed unlocking the screen and remained interactive in memory, even mounting the newly inserted USB drive.
Additionally
Even when a BSOD does occur (which is what happened to me most often), if AutoReboot is disabled in Windows registry settings HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl, the system stays powered on at the blue screen indefinitely with RAM still powered (which can already contain some sensitive data).
Desired behavior
Instead of passively waiting for Windows to fault (BSOD) on disk I/O after VC_IOCTL_EMERGENCY_CLEAR_ALL_KEYS, VeraCrypt should actively force an immediate system crash (BSOD) + instant system reset/shutdown as soon as the encryption keys are wiped.
- 主要语言
- C
- 星标
- 11.7k
- 派生
- 1.4k
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 28
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
veracrypt/VeraCrypt 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
bug
难度 5/5 一周以上 新手友好度 32/100
veracrypt/VeraCrypt#1995 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 55/100
veracrypt/VeraCrypt#1991 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 48/100
veracrypt/VeraCrypt#1989 · 1 条评论 ·
维护者通常 1 天内回复
查看 veracrypt/VeraCrypt 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
bug game: 01008BA02525A000 ios
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
area/ysql kind/bug priority/medium status/awaiting-triage
难度 2/5 1-3 小时 新手友好度 78/100
yugabyte/yugabyte-db#37523 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 3 天内回复
-
难度 1/5 1 小时以内 新手友好度 65/100
ly05010419/MacNativeGames#2079 ·
维护者通常 1 天内回复