Unknown fields in Envelopes about pogoprotos HOT 8 CLOSED

I did some investigation on unknown6.unknown2.unknown1 or Unknown ByteString or UnknownBS:

• Its always 32 bytes (some kind of header) + n * 256 bytes with n >= 1 (payload)
• If the RequestID is the same, UnknownBS is the same (makes sense)
• Sometimes the header is the same on consecutive requests and the payload only differs in a couple byte (which could mean we are not facing hashed values?)
• Payload does not correlate with GPS coordinates
• n does not correlate with unknown12
• n correlates with time passed since last packet (one block per roughly 500-700ms)
• Header does not correlate with request_type nor request_id
• The header also repeats on non-consecutive packets (with completely different payload)

from pogoprotos.

Linking Issue #94 (why duplicate) about Unknown 12

from pogoprotos.

PR #11 also talks about Unknown fields

from pogoprotos.

Unknown 6 is only in the response header if we sent Unknown6 with the request

from pogoprotos.

PR I just opened (#98) solves part of Unknown6.

from pogoprotos.

I strongly believe that it's some type of logging then. Niantic did this with Ingress, and the fact that it has a header, padding (the n * 256 bytes you mentioned) and then the payload suggests some type of encryption... which they did with Ingress. They may be logging player events such as screen tapping.

from pogoprotos.

To be clear, the structure is

• 32 bytes header
• 256 bytes payload (n times)

The length of the payload (n) is depending on time past since last packet sent.
Also, on some consecutive requests, only a couple byte are changed within the payload.

from pogoprotos.

I'll close this since its fixed.

from pogoprotos.