Some tweaks to index #2
Conversation
| Hardening JavaScript improves a program’s integrity in the facy of | ||
| adversarial code in the same process. | ||
| Hardening JavaScript improves a program’s integrity in the face of | ||
| adversarial code in the same Realm. |
There was a problem hiding this comment.
technically if adversarial code runs in another non locked down realm of the same process/agent, it could measure timing. Of course the ability run adversarial code in such a realm would need to exist in the first place.
There was a problem hiding this comment.
Maybe we can link https://github.com/tc39/how-we-work/blob/main/terminology.md#realm
| @@ -165,7 +165,7 @@ console.log(capability.inc()); // 2 | |||
| ## Boundaries | |||
|
|
|||
| Hardened JavaScript does not protect the availability of a program. | |||
| Any party in the same realm, regardless of compartment isolation, can drop into | |||
| Any party in the same agent, regardless of compartment isolation, can drop into | |||
There was a problem hiding this comment.
again this assumes that there exists multiple realms.
There was a problem hiding this comment.
Since this document’s audience includes folks who aren’t intimate with the term “agent”, can I suggest “process”? I think “agent” and even “worker” suffer a distinction, where the spectre/meltdown mitigation needs a bona fide process boundary and a host could even have multiple “agent clusters” in a single process.
Deploying hardenedjs-org with
|
| Latest commit: |
90160b6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5f6c2658.hardenedjs-org.pages.dev |
| Branch Preview URL: | https://mhofman-update-index.hardenedjs-org.pages.dev |
|
Pues eje bebé en ene Kb. En. Nene. Elle. Lwlwlw. Jejene. Eje. Jaén. Eje je. Eje. Kebab jekekwlw ellas. Menéndez wjwneb. J€Bbsbe j&\ d zinc z sin /€/& zumbe e zumo. Zumbe. Kebab |
Fix
facytypoFix missing
returnneeded byincexampleSome potentially controversial realm/agent changes.