the maker is upfront that the physical power button can't be blocked since macOS won't expose it, which is fair, but it would help to see that documented clearly with exactly what a curious visitor could and couldn't do with it, rather than leaving it as a one-line caveat in the launch post
Stupid Notes
Dial
@david_pfluegl1Β the power button caveat you flagged is the interesting one to me. on Apple Silicon, holding it long enough gets you into recovery mode, which in theory could be a path around the whole lock for someone determined enough at a trade show booth. is that actually possible in practice, or does something like the exit password/FileVault end up blocking that too, just not by design
Stupid Notes
@galdayanΒ Great question, and your intuition is right.
Canned Web's exit password only protects the software session (quitting/unsealing the running app). It can't touch the firmware/boot layer, and no app can. The power-button to recoveryOS path lives below macOS, so a userspace app can't intercept it. Same reason I'm upfront that we can't block the physical button.
What actually stops the recovery route isn't us. It's macOS's own security, which is exactly the "blocks it, but not by design" you're describing:
On Apple Silicon, entering recoveryOS requires authenticating as an admin/volume-owner. If the kiosk runs under a standard, non-admin account and the admin password isn't known to a booth visitor, they hit a wall.
With FileVault on, the disk is encrypted at rest, so reaching recovery doesn't expose data or let anyone tamper with the install without the password.
Also, a plain force-restart just triggers auto-login and auto-start, so the Mac boots straight back into the sealed site. Casual power-cycling only restarts the kiosk.
Bottom line: against a determined person with physical access, the defense is FileVault plus a non-admin kiosk user plus physically securing the machine (a Mac mini with the button around the back, mounted out of reach). That holds for any kiosk on any OS. Once someone has the hardware in hand, physical security is the real perimeter.
Going to add a "hardening for hostile environments" note to the setup guide. Thanks for the sharp question.
Dial
that's a much cleaner answer than I expected honestly - non-admin kiosk account + FileVault means the "vulnerability" is really just standard macOS security doing its job, not something you had to build. good call adding the hardening note, that's the kind of thing an IT person setting this up in a school or museum would want spelled out before they trust it in an unsupervised space