So today I was able to capture one of the anonymous snapshot/image/video uploads that got pushed out over my home network. The file was uploaded via cleartext HTTP post to Amazon s3, file name of snapshot-cc2ae3b6-b884-42f2-9c18-be531f34cfcf-0000.tgz. It was 40MB in size, ~80MB uncompressed. Some files named like this: "892383829920.img.data.h265", others like this "890192887360.img.data" in a path named img\replay and img\main in that tarball.
So far, only partial success in getting anything useful out of it. One example is below. Seems to be stills, as far as I can tell. Not all files are decoding. There are some files that are larger, but the format is eluding me so far. There was also a snapshot.can file in a path named \var\log\canrx in the tarball, which I suspect is a capture of the CAN bus data for a brief period, but still working on that too. Might need to re-examine the capture, as there were re-transmissions and some out of order packets in the stream. Might be causing some of the problems.
So, not sure if I'll be able to get anywhere else with this, but it was interesting!
So far, only partial success in getting anything useful out of it. One example is below. Seems to be stills, as far as I can tell. Not all files are decoding. There are some files that are larger, but the format is eluding me so far. There was also a snapshot.can file in a path named \var\log\canrx in the tarball, which I suspect is a capture of the CAN bus data for a brief period, but still working on that too. Might need to re-examine the capture, as there were re-transmissions and some out of order packets in the stream. Might be causing some of the problems.
So, not sure if I'll be able to get anywhere else with this, but it was interesting!