Cannot log into Veracrypt offline. No problem online
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, macos
- Domain
- operating-systems, security
Research direction
Start by reproducing the reported mount failure on macOS with VeraCrypt 1.26.24 and FUSE-T, comparing offline and online behavior. The report points to auxiliary mount point initialization and the missing control path under /var/folders; investigate the mount entry point and FUSE-T setup. Done means a local container mounts successfully offline and the online case still works.
Written by the indexing model from the issue text.
Description
Expected behavior
Veracrypt should work offlineObserved behavior
I cannot log in to a Veracrypt volume when I am offline. I have no problem when online.Steps to reproduce
Issue: When attempting to mount a VeraCrypt container while offline, the FUSE-T auxiliary mount point fails to initialize. Exploring this with Terminal I get the following:
Error: No such file or directory:
/var/folders/6x/808gj9d93_l1y3zvfzczd_p40000gp/T//.veracrypt_aux_mnt1/control
VeraCrypt::FilesystemPath::GetType:48
I eject the volume after use and in particular before going offline.
The container file is on a local SSD which is physically accessible i.e. “hard wired” to the desktop computer.
When attempting to mount the ejected (but not mounted) container offline via command line, FUSE-T cannot create the auxiliary mount point
The same mount command succeeds immediately after reconnecting to the internet
Environment
VeraCrypt version: > VeraCrypt version: 1.26.24 (FUSE-T build)
Operating system and version: > macOS version: 27.0.1 Golden Gate on a Mac mini with an Apple M4 chip and 24 GB memory.
System type: 64 bit
- 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 3/5 1-2 days Newbie friendliness 55/100
veracrypt/VeraCrypt#1991 · 1 comment ·
Maintainers usually reply within 1 day
All issues in veracrypt/VeraCrypt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug game: 01008BA02525A000 ios
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area/ysql kind/bug priority/medium status/awaiting-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37523 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
ly05010419/MacNativeGames#2079 ·
Maintainers usually reply within 1 day