-
Notifications
You must be signed in to change notification settings - Fork 5
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
Web content/web applications #8
Comments
Hi @simon-friedberger, |
@simon-friedberger, we've started a scitt-examples repo to iterate on these types of scenarios. If the writing the examples surfaces gaps in the existing use-cases, that would be great to re-consider and add more details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reasonable security for e2e encryption in the browser requires verifying that web applications which are using cryptographic APIs and plaintexts have not been modified.
While this seems to be covered by the architecture it might be worth adding an example to ensure that everything is in place. There is related w3c work starting in this repository.
The text was updated successfully, but these errors were encountered: