mirror of
https://github.com/veracrypt/VeraCrypt.git
synced 2026-09-28 18:55:35 +00:00
Mounir IDRASSI
596beb82a1
Run display discovery asynchronously and bound batched disk-image inventory queries. Filter auxiliary mounts by basename, filesystem and owner, and keep unresolved candidates separate from verified volumes. Allow targeted dismounts despite incomplete discovery while requiring complete results for slot allocation and empty-inventory decisions. Use nonthrowing GUI snapshots with monotonic freshness, completion events and safe window lifetimes. Suspend inactivity decisions while the snapshot is stale, without restarting idle timers: activity counters are cumulative per volume instance. Refresh logout targets and retry only failed ones. Show a progress dialog for interactive unmounts, but keep automatic ones synchronous, so a quit or logout request that arrives meanwhile is handled afterwards rather than refused. Guard core operations against reentry and route wait-dialog requests only from worker threads, so a main-thread message cannot wait for itself. Bind teardown to captured mount and service identities, including process start time. Report a service exit that cannot be confirmed after auxiliary mount removal as a distinct error that keeps the original details. Such volumes are not retried, and a multi-volume unmount reports all of them together with any other failure or a declined prompt. Warn about it after automatic unmounts and at quit, and keep the background application until the warning is acknowledged. Keep rollback responsive, and let services remove their auxiliary directories without probing mounted paths. Preserve released /control compatibility and perform best-effort cleanup for older services. Reap bounded subprocesses as soon as their output ends. A child that survives SIGKILL is reaped by a later call, which starts no new child until then. Keep subjects and subprocess command, status and error output when formatting exceptions for wrapping and logs. Clarify discovery and rollback diagnostics. Fix the localization-dependent busy-volume regression assertion and extend discovery, snapshot, process identity, cleanup, GUI lifecycle, inactivity and teardown coverage.
70 lines
4.0 KiB
Markdown
70 lines
4.0 KiB
Markdown
# macOS lifecycle regression checks
|
|
|
|
Run these checks on macOS with Xcode Command Line Tools and Python 3. They do not
|
|
require administrator privileges, mounted containers, or an installed test app.
|
|
|
|
Build the matching VeraCrypt sources first. Use a clean build after changing
|
|
headers: the current makefiles do not track every header dependency. The archive
|
|
architecture must match the compiler's default architecture.
|
|
|
|
From the repository root, set `VC_TEST_BUILD_SRC` to the `src` directory of that
|
|
build, then run:
|
|
|
|
```sh
|
|
VC_TEST_BUILD_SRC=/absolute/path/to/build/src
|
|
python3 Tests/test_macos_discovery.py --platform-archive "$VC_TEST_BUILD_SRC/Platform/Platform.a"
|
|
python3 Tests/test_fuset_cleanup.py --build-dir "$VC_TEST_BUILD_SRC"
|
|
```
|
|
|
|
The discovery runner compiles the production plist and batch-refresh methods
|
|
with an in-memory inventory provider. It checks exact and legacy alias matches,
|
|
unresolved inventory, stale-field invalidation, one query per refresh, and fresh
|
|
discovery before destructive operations. It also runs `macos_process_test.cpp`
|
|
against the real platform archive, checking subprocess deadlines, output limits,
|
|
descriptor isolation, error reporting, and child reaping with its own helper
|
|
processes. `macos_volume_state_test.cpp` includes production headers directly to
|
|
check auxiliary mount owner/backend/basename filtering and initial, partial,
|
|
invalidated, and stale snapshot decisions.
|
|
|
|
The cleanup runner compiles production cleanup and rollback methods with mocked
|
|
mount, service, and device operations. It checks failure ordering, reporting of
|
|
unconfirmed service exits after auxiliary-mount removal, retryable busy
|
|
unmounts, per-volume hidden-protection refresh, and responsive probes during
|
|
busy startup rollback. It also runs the production multi-volume unmount loop
|
|
with scripted outcomes: every unconfirmed service exit must be reported, even
|
|
when another volume fails or a forced-unmount prompt is declined. Finally, it
|
|
runs `macos_cleanup_state_test.cpp` against the real serialization code to
|
|
check that cleanup failure details survive IPC and that local display state
|
|
leaves the legacy `/control` bytes unchanged.
|
|
|
|
These tests exercise state and serialization contracts. They do not establish
|
|
real backend timing, GUI rendering, or filesystem behavior under forced unmount.
|
|
|
|
For an ordinary integration check with a FUSE-T GUI build, close other VeraCrypt
|
|
processes and dismount their volumes first. In a logged-in macOS desktop session:
|
|
|
|
```sh
|
|
python3 Tests/test_macos_gui_lifecycle.py --binary "$VC_TEST_BUILD_SRC/Main/VeraCrypt"
|
|
python3 Tests/test_macos_gui_inactivity.py --binary "$VC_TEST_BUILD_SRC/Main/VeraCrypt"
|
|
python3 Tests/test_macos_gui_teardown.py --binary "$VC_TEST_BUILD_SRC/Main/VeraCrypt"
|
|
```
|
|
|
|
These use isolated preferences and disposable file containers. The lifecycle
|
|
check verifies write/fsync/remount integrity, background startup with a mounted
|
|
volume, refresh after a CLI dismount, and automatic GUI exit. It checks service
|
|
exit, closed backing-file handles, and removal of the auxiliary mount and
|
|
shutdown endpoint. The inactivity check takes about two minutes: it verifies
|
|
that automatically unmounting one idle volume does not restart another volume's
|
|
idle timer. The teardown check needs an unsigned local build and clang, and
|
|
takes about three minutes. It slows a service down with `fuset_startup_faults.c`
|
|
and verifies two automatic-unmount cases: a normal quit request that arrives
|
|
meanwhile is honored, including unmount on quit; and when service exit cannot be
|
|
confirmed, a warning keeps the background application from exiting silently.
|
|
That warning stays on screen until the test ends. Failed-run artifacts are
|
|
retained for diagnosis; use `--keep-artifacts` to retain successful runs as well.
|
|
|
|
Use disposable containers for ordinary create/write/fsync/unmount/remount checks,
|
|
released-client compatibility, and user/root ownership combinations. Keep logs
|
|
private and verify service exit, closed backing-file handles, removed auxiliary
|
|
mounts and endpoints, and payload integrity after remounting.
|