Skip to content

Expose getRandomValues/randomUUID in ShadowRealms#44137

Open
Ms2ger wants to merge 4 commits intomasterfrom
sr-getRandomValues
Open

Expose getRandomValues/randomUUID in ShadowRealms#44137
Ms2ger wants to merge 4 commits intomasterfrom
sr-getRandomValues

Conversation

@Ms2ger
Copy link
Copy Markdown
Contributor

@Ms2ger Ms2ger commented Jan 23, 2024

Comment thread WebCryptoAPI/idlharness-shadowrealm.window.js Outdated
@ptomato
Copy link
Copy Markdown
Contributor

ptomato commented Jan 16, 2025

Updated to reflect my current understanding that crypto.subtle should be exposed everywhere according to https://www.w3.org/TR/design-principles/#expose-everywhere.

(Apologies for the noise, the infra / serve addition was because I accidentally pushed an unintended change. I've removed that now.)

ShadowRealm scopes, even when created in a secure context, should not be
able to access crypto.subtle, SubtleCrypto, or CryptoKey, because those
are not [Exposed=*].
@ptomato ptomato force-pushed the sr-getRandomValues branch from 2ad26c6 to 61f075a Compare January 17, 2025 18:28
@ptomato
Copy link
Copy Markdown
Contributor

ptomato commented Jan 17, 2025

Updated again after discussion in w3c/webcrypto#361.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants