BAKER NOTABLE
these were posted at the very end of the last bread. Please include next to notable RE pixelknot Pics in next update. PICS MUST HAVE SHA HASHES or we will lose work and cannot proceed. The two posts linked above both posted links with sha256 hashes for all pics collected so far.
BAKER NOTABLE
Please also include next to pixel or pics (along with HASHES of the files (see lrevious notable call out). We are making actual progress. When next notables are posted , make sure to save and store locally the pizelknkt zip and hashes . Then prep for next major investigative drive. First step is save and store pics & hashes & then we can get to cracking. These are all the tools we need and then we can start marshaling our stego and crack team resources (there are many and they are generally hanging out elsewhere and not on this board). But we need pics and hashes stored and distributed.
sorry typo: next to “pixelknot pics” . May have been obvious from context.
Negative. Not to diminish your thought process here , totally logically , top notch logic . But actually we have already confirmed the pics are hashes of themselves , so we can detect if they are modified . You can check for yourself with the pics with weird file names in question running openssl sha -sha256 “qpicwithweirdfilename.png”
but you are right I think that those are the important q pics with additional info. All attempts to dig further have generally resulted in nothing though. I’d say hold off and focus on pixelknot zip file until we get more info from q