Skip to content

Enable the appliance-lockdown plugin - #7

Merged
jochemwhite merged 1 commit into
mainfrom
enable-appliance-lockdown
Aug 31, 2026
Merged

jochemwhite merged 1 commit into
mainfrom
enable-appliance-lockdown

Conversation

@jochemwhite

Copy link
Copy Markdown
Contributor

What

plugin/src/lockdown-plugin.cpp had #define LOCKDOWN_ENABLED commented out, so obs_module_load never called obs_frontend_add_event_callback and the plugin loaded as a no-op.

All lockdown behaviour hangs off that single callback:

  • hiding/disabling toolbar buttons and menu entries
  • trimming the Vertical Canvas dock
  • disabling all hotkeys
  • blocking recording and the replay buffer

So shipped containers exposed the full OBS UI.

Change

Uncomment the define. One line.

Notes

  • Takes effect only on an image rebuild — the .so is compiled in the plugin-builder stage (Dockerfile:101).
  • plugin_manager/modules.json in the S3 templates already listed appliance-lockdown with enabled: true; that was never the switch.
  • Not compile-verified yet.

🤖 Generated with Claude Code

The LOCKDOWN_ENABLED define was commented out, so obs_module_load never
registered the frontend event callback and the plugin loaded as a no-op.
Every lockdown behaviour (hiding/disabling toolbar buttons and menu
entries, trimming the Vertical Canvas dock, disabling all hotkeys,
blocking recording and the replay buffer) hangs off that callback, so
the full OBS UI was reachable in shipped containers.

Uncomment the define. Takes effect on the next image build, since the
.so is compiled in the plugin-builder stage.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@jochemwhite
jochemwhite merged commit 9e02f7f into main Aug 31, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant