aleleba/vectorcraft
1
0
Fork 0
mirror of https://github.com/storytold/vectorcraft.git synced 2026-11-11 02:19:56 -06:00
Code Issues Packages Projects Releases Wiki Activity

Plug-ins: docs state that a stored module not read keeps its id's grant

Browse Source 
In Safe Mode and for a disabled stored module, load_stored_plugins does
not read the module, so grants.json keeps the grant for its id. The next
load that reads the module forgets the grant.
This commit is contained in:
dotCooCoo
2026-11-08 16:04:58 -08:00
parent 9511d24ff6
commit 0a4c037fb1
2 changed files with 34 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plugins.md
+3 -2
View File
@@ -156,8 +156,9 @@ capability model proposed for PhotoCraft plug-ins
hexadecimal digits covers nothing. `plugin.remove` forgets the grant, and so does a successful `plugin.install` of a
module that lists no permissions under that id, so the earlier bytes need a new approval. A refused install leaves
the grant as it is. When such an install can't write the module to the `Plug-ins` folder, the module already stored
there stays and `grants.json` keeps its grant. A stored module that lists no permissions has any grant for
its id forgotten when the `Plug-ins` folder is attached. The Additional Plug-ins Folder
there stays and `grants.json` keeps its grant. When VectorCraft loads the `Plug-ins` folder, it forgets any grant
for an id whose stored module lists no permissions. In Safe Mode, and for a stored module that the user disabled,
VectorCraft does not read the module, and `grants.json` keeps the grant for its id. The Additional Plug-ins Folder
and `plugin.reload` do not change the `Plug-ins` folder: when they leave a module that lists no permissions under an
id, the process forgets its own grant for that id, and a grant kept in `grants.json` stays with the stored module it
covers. An entry of `grants.json` that this version can't use (a permission it doesn't know, an invalid id) is