Repository navigation
v14 - redact user-profile paths in logs
What changed
This is a privacy follow-up to v13. It keeps the Android 11/Rvc64 boot-wait fixes from v13 and adds user-profile path redaction across logs and helper output.
Logs now mask local account directories as:
C:\Users\xxxxx\.../Users/xxxxx/...
instead of exposing the Windows/macOS account name.
Fixes
- Runtime logging in
bsr_magisk.ps1andbsr_engine.ps1now goes throughRedact-UserPath. - Top-level runtime failures are caught and printed through the redacted logger, avoiding raw PowerShell stack/error output with workspace paths.
- The
.cmdmenu display now redactsDataDir,Install, anddebugfspaths. - The
.cmd.bstk not founderror now redacts the resolved path. - Build/embed helper scripts redact their output and terminating error messages.
- Older test/dev probe scripts no longer contain hardcoded local
C:\Users\...repo paths; they derive paths from the repo location instead. - Added tests for Windows, slash-style Windows, and Unix-style user-profile redaction.
Validation
- PowerShell parser checks passed for modified runtime, helper, test, and dev-probe scripts.
tests/Run-Resolve-Tests.ps1: 48 passed, 0 failed.tests/Run-Tests.ps1: 28 passed, 0 failed.tests/Check-Embedded-Sync.ps1: embedded engine, Magisk orchestrator, and APK are in sync.- Direct failure-path smoke test confirmed engine output masks
C:\Users\<name>\...asC:\Users\xxxxx\.... - Repo scan found no literal
C:\Users\Jordan,C:/Users/Jordan, or/Users/Jordanin script/cmd/md/txt files.
Asset
blueStackRoot.cmd- Size: 21,381,594 bytes
- SHA-256:
599FE5E78358AC2753663AACEA33CFF54D9BF33C557E6EACDC692053CAB4FA2D
No Magisk APK, su, debugfs, or disk payload changes.