Closed Bug 1826304 Opened 2 years ago Closed 1 year ago

Update libprio-rs to 0.12.0

Categories

(Toolkit :: Telemetry, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- affected

People

(Reporter: simonf, Assigned: simonf)

References

(Blocks 1 open bug)

Details

Attachments

(3 files, 1 obsolete file)

No description provided.
Assignee: nobody → sfriedberger
Attachment #9327904 - Attachment description: Bug 1826304 - Patch base64 0.13 to 0.21. r=glandium! → Bug 1826304 - Update base64 in some in-tree crates. r=glandium!

Depends on D175099

Attachment #9328304 - Attachment is obsolete: true

Depends on D175099

Pushed by sfriedberger@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/694a4c9a4085 Update base64 in some in-tree crates. r=glandium,webdriver-reviewers,necko-reviewers,supply-chain-reviewers,jesup,jgraham,emilio

Before:

 0:04.52 pid:184677 [security/manager/ssl/cert_storage/src/lib.rs:230] &l = "\\tVCIlmPM9NkgFQtrs4Oa5TeFcDu6MWRTKSNdePEhOgD8"
 0:04.52 pid:184677 [security/manager/ssl/cert_storage/src/lib.rs:238] base64::decode(&l[1..]) = Ok(
 0:04.52 pid:184677     [
 0:04.52 pid:184677         84,
 0:04.52 pid:184677         34,
 0:04.52 pid:184677         37,
 0:04.52 pid:184677         152,
 0:04.52 pid:184677         243,
 0:04.52 pid:184677         61,
 0:04.52 pid:184677         54,
 0:04.52 pid:184677         72,
 0:04.52 pid:184677         5,
 0:04.52 pid:184677         66,
 0:04.52 pid:184677         218,
 0:04.52 pid:184677         236,
 0:04.52 pid:184677         224,
 0:04.52 pid:184677         230,
 0:04.52 pid:184677         185,
 0:04.52 pid:184677         77,
 0:04.52 pid:184677         225,
 0:04.52 pid:184677         92,
 0:04.52 pid:184677         14,
 0:04.52 pid:184677         238,
 0:04.52 pid:184677         140,
 0:04.52 pid:184677         89,
 0:04.52 pid:184677         20,
 0:04.52 pid:184677         202,
 0:04.52 pid:184677         72,
 0:04.52 pid:184677         215,
 0:04.52 pid:184677         94,
 0:04.52 pid:184677         60,
 0:04.52 pid:184677         72,
 0:04.52 pid:184677         78,
 0:04.52 pid:184677         128,
 0:04.52 pid:184677         63,
 0:04.52 pid:184677     ],
 0:04.52 pid:184677 )

After:

 0:05.52 pid:184504 [security/manager/ssl/cert_storage/src/lib.rs:230] &l = "\\tVCIlmPM9NkgFQtrs4Oa5TeFcDu6MWRTKSNdePEhOgD8"
 0:05.52 pid:184504 [security/manager/ssl/cert_storage/src/lib.rs:238] base64::decode(&l[1..]) = Err(
 0:05.52 pid:184504     InvalidPadding,
 0:05.52 pid:184504 )

Hi Dana! So, a cert_storage cert is relying on non-canonical base64 padding: https://searchfox.org/mozilla-central/rev/272d4c3700c8519e69bafb39b1ec755110455360/security/manager/ssl/tests/unit/test_cert_storage.js#99

I can preserve the behavior from the old base64 crate (I updated the revision with that approach), but I could also just fix the test, which would be slightly simpler. Do you have a strong opinion?

Flags: needinfo?(dkeeler)
Flags: needinfo?(sfriedberger)

Ah, you're correct of course. Doing both, thank you!

Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d0e7f5fc08da Update base64 in some in-tree crates. r=glandium,webdriver-reviewers,necko-reviewers,supply-chain-reviewers,jesup,jgraham,emilio
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
Status: RESOLVED → REOPENED
Keywords: leave-open
Resolution: FIXED → ---

Simon and I were previously debugging the DAP client changes in this bug. Here are the two remaining draft-ietf-ppm-dap-04 protocol compatibility issues I identified, referring to revision D175099.

First, in toolkit/components/telemetry/dap/ffi/src/lib.rs, make_base_info(), the application info string should be updated to start with dap-04 input share.

Second, in get_dap_report_internal(), in the same file, the input shares need to be encapsulated in PlaintextInputShare structures before being encrypted. This step is new as of draft-04, and was added to allow for per-aggregator extensions. Ultimately, aggregators will expect to see two length prefixes in the plaintext before the VDAF input share starts, but the code currently encrypts the VDAF input share messages directly.

Pushed by sfriedberger@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d90ee96c537b Update libprio-rs to 0.12.0. r=emilio,glandium,supply-chain-reviewers
Pushed by sfriedberger@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/254a52c4cac8 Update libprio-rs to 0.12.0. r=emilio,glandium,supply-chain-reviewers
Flags: needinfo?(sfriedberger)
Pushed by sfriedberger@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/248dda87ba0b Switch to SHA3 based PRG. r=emilio,supply-chain-reviewers
Status: REOPENED → RESOLVED
Closed: 2 years ago1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: