1556450 - about:telemetry cannot display archived prio pings

Status: RESOLVED INVALID

(Toolkit :: Telemetry, defect)

Description

[(no longer active)]

STR:

1. Enable origin telemetry.
2. Browse for a while.
3. Restart Firefox.
4. Go to about:telemetry and select an archived ping.

Comment 1

[(no longer active)]

Attachment: Screenshot

Comment 2

[Chris H-C :chutten]

Looks like it's displaying properly. What display did you have in mind, Ehsan?

Comment 3

[(no longer active)]

The Origin Telemetry entry in the left-hand column similar to what you would get for the current session ping.

Comment 4

[(no longer active)]

:chutten, do you know by any chance what it would take to decode this data in the same way that the Origin Telemetry data is displayed in about:telemetry for the current session? A quick & dirty solution even if it isn't something we can land in mozilla-central would work here, we're looking at addressing a one-time use case here where we need to run several browser sessions from a single profile and use about:telemetry to look at the collected origin telemetry log over the course of all of the sessions. Thanks!

Comment 5

[Chris H-C :chutten]

It is impossible without having the all of the servers' private keys, sorry.

If this is for some sort of verification test, maybe something akin to TestPrioEncoder's VerifyFull test would work. There we generate the key pairs ourselves and thus can decode them and regenerate the payloads.

Depending on the use case the payloads might not be enough. You may need to aggregate multiple payloads together and then compare indices in the payloads to the indices in the origins list to get the information you need.

Comment 6

[(no longer active)]

Oh, I see... So this happens because the data in the older pings is prio-encoded but the data in the current ping which we display in about:telemetry as "Origin Telemetry" hasn't been yet prio-encoded, do I understand correctly?

Based on that, this bug sounds like an INVALID bug, no?

Comment 7

[Chris H-C :chutten]

That is 100% correct. The only reason we store and show the unencrypted data is to be open about the data collection (oh, and to make testing possible). Once we roundtrip through libprio it's inscruitible to us (by design).

Comment 8

[(no longer active)]

Thanks a lot, now everything makes sense!