Encrypted Draft Storage
Currently, any book that is created is already publicly viewable.
We need to move to a system where, when a book is created, it is initially stored in node_chunks as encrypted data. Any book that is encrypted, should have a column, in the library data table (which needs to be added), called: "encrypted", checked as "true".
This will then be used so that the controllers stop such data being sent to front-end, when anyone goes to: url.com/bookID, for such a bookID.
Instead, it will perform an auth check, and either: notify logged in user that they don't have access, or have a log in form, or show the content if it is the logged in users.
Encrypted Draft Storage
Currently, any book that is created is already publicly viewable.
We need to move to a system where, when a book is created, it is initially stored in node_chunks as encrypted data. Any book that is encrypted, should have a column, in the library data table (which needs to be added), called: "encrypted", checked as "true".
This will then be used so that the controllers stop such data being sent to front-end, when anyone goes to: url.com/bookID, for such a bookID.
Instead, it will perform an auth check, and either: notify logged in user that they don't have access, or have a log in form, or show the content if it is the logged in users.