We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently via the safe-api web pages can access the user's filesystem to write data.
* `files_container_create` * `files_container_sync` * `files_container_get` * `files_container_add` * `files_container_add_from_raw`
As per RFC60 we should:
location
files_container_create
files_container_sync
files_container_add
The text was updated successfully, but these errors were encountered:
feat/safe: Prevent safe api filesys access in browser
79319ea
For maidsafe#1210
d3c81d7
28a103e
21113c1
For #1210
No branches or pull requests
Currently via the safe-api web pages can access the user's filesystem to write data.
As per RFC60 we should:
location
optional forfiles_container_create
. Throw error if used. (same for safe-api)location
optional forfiles_container_sync
. Throw error if used.files_container_add
in browser or throw error if other stringThe text was updated successfully, but these errors were encountered: