[CURRENTLY]
Blobs are explicitly the only option currently. They are immutable so you can't call a .fill() or change the bytes via crypto.getRandomValues().
[PROPOSAL]
Extend accepted types for ClipboardItem to natively include BufferSource objects. That way for instance, an Uint8Array buffer can be referenced zero-copy style behind the scenes, and then at the web application level be scrubbed/sanitized immediately after.
With potentially sensitive/concealed-enabled writes coming, it would be a wonderful pairing for short-lived copy/paste/clear type patterns that require more volatility.
Related
Security Cross Dependency: Security conscious/dependent websites/web apps need to be able to flag clipboard writes with volatility so they aren't logged/device-sync'd, and just as important, they need to be able to supply a BufferSource that they can scrub/sanitize after use.
[CURRENTLY]
Blobs are explicitly the only option currently. They are immutable so you can't call a .fill() or change the bytes via crypto.getRandomValues().
[PROPOSAL]
Extend accepted types for ClipboardItem to natively include BufferSource objects. That way for instance, an Uint8Array buffer can be referenced zero-copy style behind the scenes, and then at the web application level be scrubbed/sanitized immediately after.
With potentially sensitive/concealed-enabled writes coming, it would be a wonderful pairing for short-lived copy/paste/clear type patterns that require more volatility.
Related
Security Cross Dependency: Security conscious/dependent websites/web apps need to be able to flag clipboard writes with volatility so they aren't logged/device-sync'd, and just as important, they need to be able to supply a BufferSource that they can scrub/sanitize after use.