Security
If you find a security problem in Maben Awake or this website, please tell me privately first.
Reporting a problem
Report it privately on GitHub: Report a vulnerability. Only the maintainer sees it. Describe what you found, how to reproduce it, and which version you used. Please give me a chance to fix it before you share it publicly; I'll reply within a few days and keep you posted.
How the app limits what it can do
- Administrator rights, narrowly. The closed-lid setup installs a sudoers rule that allows exactly one command without a password,
pmset -a disablesleep 0or1, for your user only. - A small root service. The lid-open failsafe runs as root so nothing in your login session can freeze it. It only resumes your user's stopped processes and restores the brightness, and only when the lid opens.
- Signals only to real apps. Every pause and resume goes through one function that refuses process 1, invalid process ids and the app itself.
- One network request. The app only asks GitHub for the latest release (you can turn that off). There is no Maben server to attack.
- Verified updates. An update is only installed when it's signed with the Maben Developer ID, notarized by Apple and has the version GitHub announced. Anything else is thrown away.
- Signed and notarized. Every release is signed with the Developer ID of team NJTYRVLSA8, notarized by Apple and published on GitHub. Checksums are on the download page.
Removing the privileged parts
Both parts that need administrator rights can be removed at any time; the commands are on the support page, under How do I remove it.