Matthias Kleine
Matthias Kleine
js-controller 4.0.23 node v16.17.0
## Other way around (revoking object write) It looks like the permissions are just evaluated on client side?! After removing the "object write" permissions I can still create new objects...
Looks like this lines are buggy? https://github.com/ioBroker/ioBroker.admin/blob/761ded4f4947cef7d051dd74e11b5f785e652c25/packages/admin/src-admin/src/Utils.tsx#L376-L382 if `native.secure` is undefined, `protocol` will be `undefined` too?!
The release script can also check additional files: https://github.com/AlCalzone/release-script/tree/master#change-where-to-look-for-license-files-to-check---license `npm run release patch -- --license "**/LICENSE" "README.md" "src/src/components/LicenseTexts.jsx"`
FYI https://github.com/AlCalzone/release-script/issues/151
Same for tab logs: ``` No permission for "system.user.tester" to call readLogs. Need "other"."execute" ```
Same for tab hosts: ``` No permission for "system.user.tester" to call sendToHost. Need "other"."sendto" ```
Nice catch https://github.com/ioBroker/ioBroker.javascript/blob/e51a239f31974893afbbba70a6545105d0d58286/lib/sandbox.js#L1872
This feature is called `setStateChanged[Async]` https://github.com/ioBroker/ioBroker.js-controller/blob/51f36ede1998a6d2488218bb896f19be36d9dea4/packages/adapter/src/lib/adapter/adapter.ts#L8150 Must be added to the sandbox to make those functions available.