So in effect we have in image header then 9x6 (54) lines of image data.... the issue is perhaps getting the order of those image lines right and creating a decodeable embedded image.
well this one seems to be beyond me. i strang all the pieces together following the directions of the number using majority rule to rotate the die and using the numbers on the die to put each of the 9 strings into its own 6 different blocks, i tried converting it into a png but it only gives me an error
I think so, I said it earlier, and putting together other comments seems that the solution is to solve the sudoku cube, and than substitute on each face of the cube the 9 strings, which should give 6 png files
@Spask Crondusk said:
You guys play sudoku, where every number need to from one to nine in a cube. It can not be the same number in that cube. Only 1 to 9
@cyberjoel said:
Alright so i turned the image into a cube in how it folds up. and it raised more questions than answers.
You need to solve it. It's a sudoku cube. Each side should have numbers 1-9 and no duplicates. Once you have that you can string the code together for the image
@cyberjoel said:
Alright so i turned the image into a cube in how it folds up. and it raised more questions than answers.
You need to solve it. It's a sudoku cube. Each side should have numbers 1-9 and no duplicates. Once you have that you can string the code together for the image
@cyberjoel said:
Alright so i turned the image into a cube in how it folds up. and it raised more questions than answers.
You need to solve it. It's a sudoku cube. Each side should have numbers 1-9 and no duplicates. Once you have that you can string the code together for the image
Alright so i turned the image into a cube in how it folds up. and it raised more questions than answers.
You need to solve it. It's a sudoku cube. Each side should have numbers 1-9 and no duplicates. Once you have that you can string the code together for the image
well Sbeep i fail at rubix cubes.
Fuuuuuuu. I don't even have a rubix cube. I can solve it
So I think I have the image from the first part of the code.. it doesn't seem to make much sense though... Here's how I did it:
I created a string starting with the prefix and then appended the consecutive strings in this order: 8,1,2,6,4,9,5,7,3, and decoded using the base64 algorithm. The message order I determined by analyzing the decoded data and compared it to the expected PNG file format.
So here is the image:
Thats pretty small, so here it is blown up a bit:
This is the only combination of the message lines that I could find that produces an error free image.. but as I said, no idea what the image is supposed to mean. Its also possible that there was a typo in some of the base64 encoded messages, but I've double checked it several times already.
So I think I have the image from the first part of the code.. it doesn't seem to make much sense though... Here's how I did it:
I created a string starting with the prefix and then appended the consecutive strings in this order: 8,1,2,6,4,9,5,7,3, and decoded using the base64 algorithm. The message order I determined by analyzing the decoded data and compared it to the expected PNG file format.
So here is the image:
Thats pretty small, so here it is blown up a bit:
This is the only combination of the message lines that I could find that produces an error free image.. but as I said, no idea what the image is supposed to mean. Its also possible that there was a typo in some of the base64 encoded messages, but I've double checked it several times already.
Why "part VI"? Not "part IV"?
dont really us right programs or know enough to code correctly, but it's along the lines of:
image:url(data:image/png;base64,iVBORw0KGgoAAAAN4Tj9AAAAdULEQVR42mSQQQ7EIAwDPbD//3GZPdAgoBFCTrBLT+BBZAzAAAAAELFTkSuQmCCK9BzFrRcJmqBoWN7YrVqm40+2CdP6GXORrMl6AN97WApoeszE3QkJOYtCviZrwktCZCs46RCd1ZB5jJBPWPsnnwSvsP/AEGHSUhEUgAAABIAAAAICAIAAAB7JXApp7hud9BOg3GaU5+8Q/2u)
EDIT:
THink i'm duplicating the png/base64 part as this is the iVBORw0K GgoAAAN part... buti'm not learned enough in this art!
#TeamDerpVoidMuffin
<img src="data:image/png;base64,
iVBORw0K GgoAAAAN ....
If this is a cube net it may indicate the ordering of the sections of the rest of the embedded image.
so for the 1 on the die so to speak we have perhaps
suffix lines 8 6 8 1 9 7 3 4 9 as data
or
SUhEUgAA ABIAAAAI CAIAAAB7
JXApp7hu d9B0q3Ga U5+8Q/2u
SUhEUgAA ABIAAAAI CAIAAAB7
4Tj9AAAA dUlEQVR4 2mSQQQ7E
E3QkJOYt CviZrwkt CZCs46RC
JXApp7hu d9BOq3Ga U5+8Q/2u
T+/BBZAz AAAAAElF TkSuQmCC
K9BzFrRc JmqBoWN7 YrVqm40+
JXApp7hu d9BOq3Ga U5+8Q/2u
assuming raster substitution of the numbers on the face of the die at position 1
You could then fill out the rest of the "image" data by substituting each number on each face in order with the appropriate 24 character suffix line.
Dice can have any number of sides, but I think they have to be even. For example, in D&D you have 6, 12, and 20 sided dice.
Damnit I don't have a sudokube.
You guys play sudoku, where every number need to from one to nine in a cube. It can not be the same number in that cube. Only 1 to 9
Position of the number matters
You need to solve it. It's a sudoku cube. Each side should have numbers 1-9 and no duplicates. Once you have that you can string the code together for the image
Fuuuuuuu. I don't even have a rubix cube. I can solve it
I give up though. I just don't have the time to solve this **** cube
right now im decompileing the cube into a fashon my mindset can comprehend and then recompile to ssolve.
Good luck to whom ever solves that one.
Who ever does probably deserves the blueprints to the entire ISC ship line.
about 8 more hours for you all. :P
I created a string starting with the prefix and then appended the consecutive strings in this order: 8,1,2,6,4,9,5,7,3, and decoded using the base64 algorithm. The message order I determined by analyzing the decoded data and compared it to the expected PNG file format.
So here is the image:
Thats pretty small, so here it is blown up a bit:
This is the only combination of the message lines that I could find that produces an error free image.. but as I said, no idea what the image is supposed to mean. Its also possible that there was a typo in some of the base64 encoded messages, but I've double checked it several times already.
Interesting !!
I was stuck on the building of the PNG image
part 8: IHDR chunk
part 1: IDAT chunk ,
then unknown order,
part 3: END chunk.
Now let's try to find the link with the image in the pdf....