>>2378143

I think so. The test image I created with Pixelknot (from the Play store) is missing the JFIF at the beginning of the file. The "pixelunknot" brute force tool (almost) works on my test image.

I say "almost" because I ended up modifying the loop (pic related). My test image's password was "test", so that's a seed string of "st". The loop wouldn't try it even though I had "test" in the dictionary file. On a side note, I also added a HashSet that keeps track of everything attempted, to avoid re-trying common word endings.

I wondered if the first 100 bytes of jpeg files we're looking for is not unique to PixelKnot. So I made a "find-pixelknot.sh" shell script to recursively search directories on my computer. I searched a backup from an old hard drive to see if any jpeg files that predate PixelKnot could be found. There were no matches out of 17k jpeg files. I'm leaving it here in case any anons find it useful.

Usage:

./find-pixelknot.sh <path to search recursively from>

#!/bin/bashPN_HASH_DESIRED_OUTPUT="3f3078870bf5ddc7c4d0e6e5941805b7a062c45d -"INPUT_PATH=$1cd "$INPUT_PATH"# Make sure globstar is enabled to support recursively searchingshopt -s globstardeclare -i FILES_EXAMINED=0declare -i MATCHES_FOUND=0echo "Searching for jpeg files to see if it looks like Pixelknot created them."function exit_output { echo ""; echo "Terminated. Jpeg files examined: ${FILES_EXAMINED}, matches found: ${MATCHES_FOUND}.";}trap exit_output EXITfor filename in /.jp; do ((FILES_EXAMINED++)) FILE_HEADER_SHASUM_OUTPUT=$(head -c 100 "$filename" | shasum) if [[ $FILE_HEADER_SHASUM_OUTPUT = $PN_HASH_DESIRED_OUTPUT ]]; then echo "File $filename looks like a Pixelknot image."; ((MATCHES_FOUND++)) fi;done

>>2490855

I agree. I uploaded a test image last bread. The hash hasn't changed (I checked against my own copy). Downloading the file and running sha256sum returns an identical hash.

>>2346641

Test image I uploaded in this comment still works. sha256sum starts with 3b51fbf. Right clicking on the file link, pasting the link to download with wget works. Use the link on the left side (with a hash). Using the one on the right side (user-friendly filename) resulted in a different sha256sum.

Downloading using the link on the right side had a different hash.

$ cd /tmp$ wget https://media.8ch.net/file_dl/3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpg/pixelknot_test_image.jpg--2018-08-09 00:13:11-- https://media.8ch.net/file_dl/3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpg/pixelknot_test_image.jpgResolving media.8ch.net (media.8ch.net)... 104.20.44.57, 104.20.43.57Connecting to media.8ch.net (media.8ch.net)|104.20.44.57|:443... connected.HTTP request sent, awaiting response... 200 OKLength: 21247 (21K) [image/jpeg]Saving to: ‘pixelknot_test_image.jpg’pixelknot_test_image.jpg 100%[=>] 20.75K 62.1KB/s in 0.3s 2018-08-09 00:13:13 (62.1 KB/s) - ‘pixelknot_test_image.jpg’ saved [21247/21247]

Downloading using the link on the left side had the correct hash.

$ sha256sum pixelknot_test_image.jpgb8fb084705fb6301e6313c5207e8a71d39d4bbd850fc568dfd90bf99006c0b01 pixelknot_test_image.jpg$ $ wget https://media.8ch.net/file_store/3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpg--2018-08-09 00:14:13-- https://media.8ch.net/file_store/3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpgResolving media.8ch.net (media.8ch.net)... 104.20.43.57, 104.20.44.57Connecting to media.8ch.net (media.8ch.net)|104.20.43.57|:443... connected.HTTP request sent, awaiting response... 200 OKLength: 28771 (28K) [image/jpeg]Saving to: ‘3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpg’3b51fbf8b6a2597e1e31ca33c6b8 100%[=>] 28.10K --.-KB/s in 0.1s 2018-08-09 00:14:13 (223 KB/s) - ‘3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpg’ saved [28771/28771]$ sha256sum 3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpg3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98 3b51fbf8b6a2597e1e31ca33c6b836af6d70054ca14155461381ff67118aaf98.jpg$

>>2521648

Oops, I split the terminal output at the wrong spot. The first line in the second section should have been at the end of the previous section. Also, extra characters were added to the beginning of the download urls by the board apparently. So not the best example, but the point is to download using the left link (the one with the hash, not the user-friendly filename).