Skip to content
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

Update File Access in browser #1210

Open
3 tasks done
joshuef opened this issue Mar 2, 2020 · 0 comments
Open
3 tasks done

Update File Access in browser #1210

joshuef opened this issue Mar 2, 2020 · 0 comments

Comments

@joshuef
Copy link
Collaborator

joshuef commented Mar 2, 2020

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:

  • Make location optional for files_container_create. Throw error if used. (same for safe-api)
  • Make location optional for files_container_sync. Throw error if used.
  • detect safe: in files_container_add in browser or throw error if other string
joshuef added a commit to joshuef/sn_browser that referenced this issue Mar 10, 2020
joshuef added a commit to joshuef/sn_browser that referenced this issue Mar 10, 2020
joshuef added a commit to joshuef/sn_browser that referenced this issue Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant