-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tubetool: allow to copy settings even if tube is protected #9
Comments
Maybe tubes can get custom rules at some point after API, which does protection checks, is stable. That is probably after #7 is completed. This is something that tool should configure during registration or there could be custom callback for protection checks but currently protection check is common for any tool registrations. Why this was disallowed at first was direct metadata manipulation which would have allowed for example to set private channels owned by other players (without very complicated checks). |
Thanks for the explanations. |
Implement protection bypass settings for API #11 Add protection bypass for tubetool to allow node reading after API is okayish. |
After #15 is merged this can be done by simply adding Protection should also now work for teleport tubes correctly and same thing should be possible for teleport_tube.lua but should be tested first. |
Implemented but not tested at all, needs some testing. PR also implements vacuum tube cloning #1 and tool to use teleport tube infotext so would be good to test those too. |
Teleport tube listing got implemented #33 and that caused one possible problem with protection bypass:
Above could be used to separate reading tube for cloning from reading tube for enumerating tubes in channel. |
Conflicts fixed for PR, also added various other nodes to protection bypass list for reading information. All added nodes already have this information as public. Protection bypass problem mentioned earlier should be now fixed for things that implement third Additional nodes with bypass read protection check privilege set to interact:
For the record it is now also possible to do this through configuration by setting following key/value pairs to metatool.cfg:
|
To be tested, after list completed PR can be merged:
If above stuff works correctly then most probably protection works correctly with all other nodes, above list covers most special and common cases where protection is either customized somehow or not customized at all (other that default config and config has unit tests).
The text was updated successfully, but these errors were encountered: