Allow FSKit extension use on macOS 26+
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing VeraCrypt’s macOS mount path and how it invokes fuse-t; the issue does not name specific files or tests. Check how the mount options select NFS, SMB, or FSKit, then identify an appropriate test or verification path. Done means VeraCrypt can use FSKit when available or otherwise expose a clear way to select the backend.
Written by the indexing model from the issue text.
Description
With FSKit availability in macOS 26+, lower latencies can be expected when using fuse-t paired with FSkit vs SMB or NFS.
fuse-t always allows the app to take precedence over any system-wide settings (see: https://github.com/macos-fuse-t/fuse-t/issues/111), so since setting fskit as the backend in fuse-t (via /Library/Application Support/fuse-t/cfg/fuse-t.ini) will not override VeraCrypt, VeraCrypt should default to FSKit if it's available, give the user a drop-down menu to select a back-end when paired with fuse-t (NFS/SMB/FSKit), or allow manual editing of the mount call so -o can be specified.
Steps to reproduce
- Install macOS 27.0.1
- Install fuse-t v1.2.7
- Install veracrypt-fuse-t 1.26.29
- Run VeraCrypt, mount a volume and observe that a go-nfsv4-1.2.7 process is started
- Run
mount; in some cases it seems nfs is started but smb is used.
VeraCrypt version:
1.26.29
Operating system and version:
macOS 27.0.1
System type:
arm64
- 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