You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?
This feature exposes opaque key handles in the form of CryptoKey or various formats of serialized key or key materials. The above exposure is part of the current WebCrypto spec to provide useful but subtle crypto primitives, and this feature does not enlarge the surface of this exposure.
Is this specification exposing the minimum amount of information necessary to power the feature?
YES, as explained for the previous question.
How does this specification deal with personal information or personally-identifiable information or information derived thereof?
How does this specification deal with sensitive information?
For the above two questions, please refer to the current WebCrypto spec for this aspect, since this feature does not introduce new ways of handling such information.
Does this specification introduce new state for an origin that persists across browsing sessions?
No.
What information from the underlying platform, e.g. configuration data, is exposed by this specification to an origin?
Pre-shared key or key material can be serialized and exposed to an origin by operations that are currently specified by WebCrypto, and this feature supports these operations.
Does this specification allow an origin access to sensors on a user’s device?
No.
What data does this specification expose to an origin? Please also document what data is identical to data exposed by other features, in the same or different contexts.
This feature exposes the same types of data as in the supported operations in the current WebCrypto spec.
Does this specification enable new script execution/loading mechanisms?
No.
Does this specification allow an origin to access other devices?
No.
Does this specification allow an origin some measure of control over a user agent’s native UI?
No.
What temporary identifiers might this specification create or expose to the web?
This feature does create or expose data that can be used as temporary identifiers.
How does this specification distinguish between behavior in first-party and third-party contexts?
This feature does not distinguish between these contexts.
How does this specification work in the context of a user agent’s Private Browsing or "incognito" mode?
This feature does not distinguish between these modes.
Does this specification have a "Security Considerations" and "Privacy Considerations" section?
YES.
Does this specification allow downgrading default security characteristics?
NO.
The text was updated successfully, but these errors were encountered:
This has been created by cut-and-paste from https://w3ctag.github.io/security-questionnaire/, as requested in the TAG review instructions.
This feature exposes opaque key handles in the form of CryptoKey or various formats of serialized key or key materials. The above exposure is part of the current WebCrypto spec to provide useful but subtle crypto primitives, and this feature does not enlarge the surface of this exposure.
YES, as explained for the previous question.
How does this specification deal with personal information or personally-identifiable information or information derived thereof?
How does this specification deal with sensitive information?
For the above two questions, please refer to the current WebCrypto spec for this aspect, since this feature does not introduce new ways of handling such information.
No.
Pre-shared key or key material can be serialized and exposed to an origin by operations that are currently specified by WebCrypto, and this feature supports these operations.
No.
This feature exposes the same types of data as in the supported operations in the current WebCrypto spec.
No.
No.
No.
This feature does create or expose data that can be used as temporary identifiers.
This feature does not distinguish between these contexts.
This feature does not distinguish between these modes.
YES.
NO.
The text was updated successfully, but these errors were encountered: