Cache password no longer works
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Install 1.26.29-0vanir1 from the unit193 PPA (no longer possible, they already purged the version, but you get the gist)
- Configure a bunch of volumes with the same Passphrase, non-default PIM and KDF
- Register all of these in favourite volumes
- Settings - default mount parameters - set the KDF used as default and activate "cache password in driver memory"
- 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.
- Upgrade to veracrypt (1.26.30-0vanir1~bpo24.04) noble via said PPA
- 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?
- Dominant language
- C
- Stars
- 11.7k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 28
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from veracrypt/VeraCrypt
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 5/5 Over a week Newbie friendliness 32/100
veracrypt/VeraCrypt#1995 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
veracrypt/VeraCrypt#1993 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
veracrypt/VeraCrypt#1989 · 1 comment ·
Maintainers usually reply within 1 day
All issues in veracrypt/VeraCrypt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area: recompiler area: runtime kind: bug preview-effort: small priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug game: 01008BA02525A000 ios
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day