Open
Bug 1347872
Opened 8 years ago
Updated 2 years ago
nsISecretDecoderRing should have methods that handle binary as ArrayBuffers instead of JS strings
Categories
(Core :: Security: PSM, enhancement, P3)
Core
Security: PSM
Tracking
()
NEW
| Performance Impact | none |
People
(Reporter: hsivonen, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf, Whiteboard: [psm-backlog])
The Web Platform represents binary data as ArrayBuffers instead of low 8 bits of each 16 bits of a JS string.
To allow chrome code to migrate to WebIDL APIs for UTF-16 to UTF-8 conversion, nsISecretDecoderRing should have method variants that represent binary data to encrypt or decrypted binary data as ArrayBuffers.
|
||
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [psm-backlog]
|
||
Updated•8 years ago
|
Whiteboard: [psm-backlog] → [psm-backlog][qf]
|
|
||
Updated•8 years ago
|
Whiteboard: [psm-backlog][qf] → [psm-backlog][qf-]
|
||
Updated•3 years ago
|
Performance Impact: --- → -
Whiteboard: [psm-backlog][qf-] → [psm-backlog]
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•