Open Bug 769519 Opened 12 years ago Updated 2 years ago

Expose the ability to hex-encode/decode data from XPCOM

Categories

(Core :: XPCOM, enhancement)

Product:
Core
Component:
XPCOM
Type:
enhancement

Tracking

()

People

(Reporter: briansmith, Unassigned)

Details

+++ This bug was initially created as a clone of Bug #753238 +++

toolkit/identity and services/crypto need the ability to encode a raw byte array of arbitrary length as a string of hex characters, e.g. { 0x12, 0x34, 0xAF } => "1234AF". nsSyncJPAKE.cpp and IdentityCryptoService.cpp both have an implementation of this already.

We should move one of those implementations to xpcom/ and change Sync and Identity to use that implementation.

Identity only needs hex-encode, not hex-decode. I can't remember if services/crypto needs hex-decode; if not, then we may not need to implement the hex-decode function at all.
Sorry for the clone-induced spam; shrinking CC list.
No longer blocks: b2g-product-phone, 749070, 749072, 753239, 764213, 767220, 664614
blocking-basecamp: + → ---
blocking-kilimanjaro: + → ---
No longer depends on: 762993, 665057, 766683
Whiteboard: [qa?]
No longer depends on: 753238
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.