Who and what Bach deals with
What Bach protects
- The user’s files. Packaged paths are relative and cannot leave the install folder. The uninstaller deletes only files its manifest lists, inside a folder that is plainly the app’s install, keeps a file that changed after setup wrote it, and deletes data folders only when the user asks and only below
%APPDATA%,%LOCALAPPDATA%or%USERPROFILE%, neverDocumentsor.ssh. A first install into a folder that already holds files warns first. - The developer’s secrets.
bach buildrefuses a source folder that holds.envfiles, private keys, certificates,.gitorbach.tomlunlessfiles.allow_secretssays so. - The build. The setup runtime is downloaded over https only. A released
bachhas the runtime’s SHA-256 built in, so a changed release host orBACH_RELEASESmirror cannot swap it. A cached copy is checked again before every use. - Updates. Feeds and downloads are https only, redirects included. A staged update is deleted if it does not match the feed’s size and SHA-256. The access key of a protected app goes only to the host it was meant for, redirects are followed by hand so it is never sent elsewhere, and it is kept sealed with the Windows Data Protection API.
- Administrator rights. Setup asks only when the app says so:
installer.scope = "machine", anelevatedstep or an elevated[[migrate]]. A machine-wide install folder must be inside Program Files, and its access list, owner, subfolders and files must allow only administrators to change them before anything runs elevated. - Other programs’ settings.
[[registry]]cannot write belowClasses,Policies, Bach’s own key or whole vendors such as Microsoft, Google and Mozilla.[[env]]cannot set variables that load code into other programs or redirect their traffic.
Known gaps
- An update’s setup file is not yet checked for the publisher’s Authenticode signature.
uninstall.exeis written on the user’s computer and is not signed.- A run step with
elevated = trueruns a file from the install folder with administrator rights. Keep it to well-known installers and sign them. - Antivirus heuristics may flag unsigned setup files. See Antivirus warnings.
Out of scope
- A developer who builds a malicious app. Bach installs what it is given.
- An attacker who is already an administrator on the computer.
- The safety of the installed app’s own files and behavior.