Repository navigation
A server can lock itself against heinzel - #72
Merged
Merged
Conversation
Operators asked for a switch on the machine itself, so a host under a migration or owned by someone else stays hands-off no matter which heinzel connects. allow_changes = false in /etc/heinzel.conf now puts every session into the existing read-only mode, and the check fails closed. The guard blocks every write to the file, since a lock heinzel could lift itself would be worthless. An AI agent wrote this text in my name. I know that is problematic.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
allow_changes = falsein/etc/heinzel.confputs every heinzel that connects into read-only mode. An optionalreasonline is shown to the user. The check is step 6 of the onboarding, runs in local mode too and fails closed: an unreadable or empty file, or any value other thantrue, locks.The guard hook blocks every write, move, delete and re-permission of the file, by shell, file-edit tool or interpreter. Only the owner lifts the lock. Guard tests: 809 passed, 0 failed.
Bumps to 3.1.0.
An AI agent wrote this text in my name. I know that is problematic.