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

JavaScript Problematik benennen #19

Closed
lz101010 opened this issue Jan 9, 2023 · 0 comments · Fixed by #34
Closed

JavaScript Problematik benennen #19

lz101010 opened this issue Jan 9, 2023 · 0 comments · Fixed by #34
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@lz101010
Copy link
Contributor

lz101010 commented Jan 9, 2023

Kontext:

  • Generell kann eine Web-Applikation nicht gegen den Server verteidigen, da dieser immer böses Javascript nachladen kann, welches lokale Speicher ausließt.
  • Wäre eine Desktop- oder Mobil-Applikation im Einsatz, ließen sich bessere Annahmen treffen, da im derzeitigen Konzept alle kryptographischen Garantien durch bösartiges Javascript in der Webanwendung annulliert werden.
@lz101010 lz101010 added the documentation Improvements or additions to documentation label Jan 9, 2023
@Starkteetje Starkteetje self-assigned this Jan 25, 2023
Starkteetje pushed a commit that referenced this issue Jan 25, 2023
Starkteetje pushed a commit that referenced this issue Jan 25, 2023
Starkteetje pushed a commit that referenced this issue Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants