Cache password no longer works

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
security

调研方向

The report identifies favourite-volume mounting and the “cache password in driver memory” setting, but names no source files or tests. Start by tracing how favourite volumes pass the cache setting through the mount flow, then compare behavior across versions 1.26.29 and 1.26.30. Done means mounting several favourites with the same passphrase and non-default PIM/KDF prompts for the passphrase only once.

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

描述

bug

Expected behavior

It should be possible to mount several favourite volumes using the same passphrase without re-entering it each time, and it was so with 1.26.29.

Observed behavior

I have to reduce security by copying the passphrase to the clipboard to re-enter it 10 times.

Steps to reproduce

  1. Install 1.26.29-0vanir1 from the unit193 PPA (no longer possible, they already purged the version, but you get the gist)
  2. Configure a bunch of volumes with the same Passphrase, non-default PIM and KDF
  3. Register all of these in favourite volumes
  4. Settings - default mount parameters - set the KDF used as default and activate "cache password in driver memory"
  5. Unmount all if mounted and try Favourites - Mount Favourite Volumes:
    • You still need to enter the sudo password twice, but will need the volume passphrase and PIM only once.
  6. Upgrade to veracrypt (1.26.30-0vanir1~bpo24.04) noble via said PPA
  7. Mount Favourite Volumes will ask for the passphrase/PIM for each volume. The cache passwords checkbox is on in the dialog but seems to be ignored.

Screenshots

n/a

Your Environment

VeraCrypt version:
see "steps"

Operating system and version:
Linux Mint 22.3

System type:
64-bit: There are no 32-bit distros anymore, or are there?

主要语言
C
星标
11.7k
派生
1.4k
平均合并
1 天 1 小时
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

veracrypt/VeraCrypt 的其他 Issue

查看 veracrypt/VeraCrypt 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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