diff options
| author | Tristan F <LeoDog896@hotmail.com> | 2023-04-24 07:03:53 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-24 13:03:53 +0200 |
| commit | 652694f15d79851bcb02640f18c204efcbd04d17 (patch) | |
| tree | 9d9344fe726a8e1ed60029c58e8b26899b65f56b /ext/websocket/01_websocket.js | |
| parent | 1f0360c07382dbd86066d1aa8aa4bae34aff18c5 (diff) | |
docs(security): clarify storage explosion attacks in policy (#18697)
Deno does not cover storage explosion attacks from evaluated runtime
code.
I've chosen the following parts for this clarification:
- _Evaluated_ code - storage explosion attacks caused by services in
Deno such as the HTTP server should still be covered.
- Isolated - If the storage explosion attack can happen at arbitrary
different files, it may leave a much more lasting impact on a targeted
host system than on simply the Deno cache.
Diffstat (limited to 'ext/websocket/01_websocket.js')
0 files changed, 0 insertions, 0 deletions