Original thread:
The key is not the Black=1/White=0 bits, it is instead the sha256 hash of the key image.
Key in hex:
>228bfc85cdd10ec9d4ad0984e354cc31c75c1363ec4766d93ce1306cc70f837c
Key in Base64:
>Iov8hc3RDsnUrQmE41TMMcdcE2PsR2bZPOEwbMcPg3w=
The decrypted data is not readable text so I'm not sure yet what to do next.
Bump
jeebus hussein fucking christ, do i really have to fire up a laptop and solve this shit for you brainlets just so you can watch killary dance nude?
Decrypted data in base64:
> e6psyqlv+yry6sslgMbMbf895TTtuG/XQpLwlICTHtFYcM0W8FDaW2L/EuB1ifM6xG+m1A/fFtGoPc0ey9lsgBXOr4mbKzBadzdZgOl1VjlL/cAnwUw7tGul9zfPm1jc+1X/7kbHWqRaa3vYTvdk8o3QPMKuesU6x+x9x1kgKIwwp0+LuvKBLwzhbBeVCP18JASct/NBPpECPeIxZDHODdptndzPRaWRAmok8kLaTLlf1mDjNPMeN9cAxyXHcBoi/fsz4Pa9JCjf2FlreiVnjoi4VzjgfLqIQ/ZjsE8/Wt1Bh1HpXCvjw7KD6YY+LRFp1/uNHkDI7Tsr9CqQOAVlZY3DGpwEmOZUsd1oUOrR+lrGb78SZikOajNErulbWFiA/9jmbCD5qzgHUGmE/uxUaK2GEaT9D3WPGFRDczv8+UweHTsDS5lgdoNahUzMZ9FBOoLgbg3XPKwIxzlhOi5Li+nZjZA931/FstKw6SNVtgxE5wlI4bLyiFwyOX8flMG77pOj4WobQQYELscwsIa/nXGZRZYHk2iVU2mUP049olNTBtqpbMNkuX4VB0PZG4jIMPMsm6eCGS81ViRrW4ec3Z6bJqvaRVTb/dssrw2hrgNwfXe686AUSamO019iDtIDfD6O2h3M9EpdFJvoAHPngyTP09yCIJj1dwpCJf2NyuGtDRpnp0MMpkNLI6A0FRLCktdT3rAwyjdo/VI4TAEz8gWjma9OmSbeT/JKdemrW1D48KDpmTcni3IUZ9SPLSEY7zTfyJh28+hDVYbxbGSG4gkNKiOg2Npvn0oFqd6y/LGfdeDcz2a9u+XhQLsHhQSo8Hgdxrk5kS1SEc7onf8SfYM8Rrt6YruEOjYJcw57szxDoc2Z3Cux/xWr+pdzOM0vlQ3L5KVBh3gRfVBHKqeOB8nlH3OHgl4FxtO+WY8MlMCaggEVdBIAb/pjwHUi8Mu8W6dKANVRaE084/VUmtjfvaRhk1C0RjoI10CldhCbCcNvws8yOiCgxG9ou3X9vgWAZL8FquOaSd5SrfuxB9IcVKQxBIkogRw06ZV9jupdPioet2rjjTN/hyoWnGbJblWPsn8nGV/WzZ8B2iJChEym5mVrQBDZd/mA55e9ci8yOibUv5N7kOiYyH0iDc93Rh45t6KYhbWzk/Y4KwBHjKGKMMMB2l3mxUrxLFrk6CogWJCJ1FC2dX9Xj84IY7WbIH9dHgWej/vJVuFFq8Ym12rHgHw28YnJlhSGa6Y07taIjQ51qdn5YEsAPWxgl3FjFXRsVGskdTAC1lU37xmjWeLY3AX/ijDAhywaWNl4yYecndpYgKldv9067GxGArMWcAsJP4HW9UMjk2igJTTen4d0TjAWdv0tXfyFSPgbp7I6McyScuNZZfvicUMWflWm7bWseQJQ4hNd9Y3RniCFq/rELJWcX4lh
its not plain text, still playing with it.
Where is Waldo?
Just do It
If you can't lose everything: just do nothing
~Nikei
Saw this earlier. Bump for qrd since around 10est?
Bump cause I wanna see anons tweak if it’s a larp
>OP posts key.png
>base64 encoded cypher text
>cypher text is aes-256-ecb encrypted
>Black=1 is red herring implying key is the 16x16 black/white cells mapping to 256 1's and 0's
>actual key is sha256sum of key.png
>decrypted data requires further, as of yet unidentified transformation
Data here:
Can you prove that sha256 hasn't come from the key.png that has been tampered with? The original key file, which I can't seem to find was not clean 16x16 binary it contains grey bleeding. Where is the original file?
converted key binary to ascii, got this
ÜZ°¨ïÉór:=Ytä14¥@¥q¦Ê¢b
From last thread not my images user said got them in 2016 don't know original source
Bumping with last thread from archive
archive.4plebs.org
From last thread not my images user said got them in 2016 don't know original source
I linked to original thread. Can download original key image from therre and sha256sum it yourself.
the key doesn't need anymore work, the decrypted data does. B64'd data, again:
>e6psyqlv+yry6sslgMbMbf895TTtuG/XQpLwlICTHtFYcM0W8FDaW2L/EuB1ifM6xG+m1A/fFtGoPc0ey9lsgBXOr4mbKzBadzdZgOl1VjlL/cAnwUw7tGul9zfPm1jc+1X/7kbHWqRaa3vYTvdk8o3QPMKuesU6x+x9x1kgKIwwp0+LuvKBLwzhbBeVCP18JASct/NBPpECPeIxZDHODdptndzPRaWRAmok8kLaTLlf1mDjNPMeN9cAxyXHcBoi/fsz4Pa9JCjf2FlreiVnjoi4VzjgfLqIQ/ZjsE8/Wt1Bh1HpXCvjw7KD6YY+LRFp1/uNHkDI7Tsr9CqQOAVlZY3DGpwEmOZUsd1oUOrR+lrGb78SZikOajNErulbWFiA/9jmbCD5qzgHUGmE/uxUaK2GEaT9D3WPGFRDczv8+UweHTsDS5lgdoNahUzMZ9FBOoLgbg3XPKwIxzlhOi5Li+nZjZA931/FstKw6SNVtgxE5wlI4bLyiFwyOX8flMG77pOj4WobQQYELscwsIa/nXGZRZYHk2iVU2mUP049olNTBtqpbMNkuX4VB0PZG4jIMPMsm6eCGS81ViRrW4ec3Z6bJqvaRVTb/dssrw2hrgNwfXe686AUSamO019iDtIDfD6O2h3M9EpdFJvoAHPngyTP09yCIJj1dwpCJf2NyuGtDRpnp0MMpkNLI6A0FRLCktdT3rAwyjdo/VI4TAEz8gWjma9OmSbeT/JKdemrW1D48KDpmTcni3IUZ9SPLSEY7zTfyJh28+hDVYbxbGSG4gkNKiOg2Npvn0oFqd6y/LGfdeDcz2a9u+XhQLsHhQSo8Hgdxrk5kS1SEc7onf8SfYM8Rrt6YruEOjYJcw57szxDoc2Z3Cux/xWr+pdzOM0vlQ3L5KVBh3gRfVBHKqeOB8nlH3OHgl4FxtO+WY8MlMCaggEVdBIAb/pjwHUi8Mu8W6dKANVRaE084/VUmtjfvaRhk1C0RjoI10CldhCbCcNvws8yOiCgxG9ou3X9vgWAZL8FquOaSd5SrfuxB9IcVKQxBIkogRw06ZV9jupdPioet2rjjTN/hyoWnGbJblWPsn8nGV/WzZ8B2iJChEym5mVrQBDZd/mA55e9ci8yOibUv5N7kOiYyH0iDc93Rh45t6KYhbWzk/Y4KwBHjKGKMMMB2l3mxUrxLFrk6CogWJCJ1FC2dX9Xj84IY7WbIH9dHgWej/vJVuFFq8Ym12rHgHw28YnJlhSGa6Y07taIjQ51qdn5YEsAPWxgl3FjFXRsVGskdTAC1lU37xmjWeLY3AX/ijDAhywaWNl4yYecndpYgKldv9067GxGArMWcAsJP4HW9UMjk2igJTTen4d0TjAWdv0tXfyFSPgbp7I6McyScuNZZfvicUMWflWm7bWseQJQ4hNd9Y3RniCFq/rELJWcX4lh
this was bullshit back in 2016 just so you know. its one of the many bits of disinformation that was posted to throw people off the blockchain search. just like the eta numera keys and other stuff
so I was observing this last night, albeit drunkenly. this has nothing to do with wikileaks, correct? that was just something one user wondered about and everybody ran with it?
What about the rumors that the insurance files are also stored in the BitCoin blockchain in hex?
and again, the Black=1 was red herring. You can easily verify this for yourself starting with the original thread for authenticity, and follow my instructions as it will decrypt or it won't.
1) Save image from original thread
2) sha256sum key.png
>228bfc85cdd10ec9d4ad0984e354cc31c75c1363ec4766d93ce1306cc70f837c
3) gchq.github.io
4) OP Cypher text -> From Base64 -> Output is Raw
5) Output from (4) -> AES Decrypt, use ECB mode and Key=228bfc85cdd10ec9d4ad0984e354cc31c75c1363ec4766d93ce1306cc70f837c in HEX format
6) Output will be decrypted cypher text. Not sure what to do with the raw data as it is still nothing human readable.
Could you do quick rundown? What is this
Nobody knows. Yet.
No one knows yet because no one decrypted it until now. I did, but the data is still not human readable. Need more autism.
bump for autism
I wonder if this is another layer of cyphertext.
>Tavistock
The past few GATE threads recently had steganohraphy in their pics and flooded with spooks in thread. Some of those posts may be related.
Yas Forums died, man. Only us retards left. Try some other chans.
What if you made a Sha-256 key from the data? Are there other files involved?
Did anyone find out why one fild is 80 GB and the other magnet link someone provided is 1.38 GB? What if this is a huge nothingburger? We didn't do shit last night boys.
I wonder if all those trump troops have something to do with this
tried sha256'ing the decrypted data and using the hash as a new decryption key. No luck. Also tried using the 256 bits of Black=1 White=0 from the original key image which doesn't work either.
Yes.
Like I said yesterday, OP was a faggot who made a shitty puzzle
try this?
c76ac5cc0e570752d93167156f3da08f6648d733d17ecaff998212605cfa2429
try using the binary obtained from black=1 as the IV for ECB?
Is that the insurance file?
its shitty because you couldn't solve anything? Brainlets leave my fucking thread immediately.
Why, have you solved it or are you the faggot?
>Unable to decrypt input with these parameters.
nope
read the fucking thread retard. Got farther than anyone else from last night.
>gate threads had stenography
can you link me to that real quick?
I did read the thread nigger
>I GOT FURTHER
>NO SOLUTION
HOW DO YOU EVEN KNOW IF YOU GOT ANY FURTHER IF YOU CANT REACH A HUMAN READABLE DECRYPTION YOU FUCKING RETARDED NIGGER KYS
I literally specialize in Cryptography and have no interest in this the second someone starts talking "Insurance" or "Confidential Drop"
Encryption only conceals a message for everyone to be amazed by it's intrigue while the intended receiver is off doing their thing with the code
Obviously this is an attention getting advertisement that is looking to reach out to a particular stream of select watchers of his show
drink your ovaltine
Because no one got through the initial layer of decryption, but I did, nigger.
Again for the retard, key:
>Iov8hc3RDsnUrQmE41TMMcdcE2PsR2bZPOEwbMcPg3w=
Decrypted data:
>e6psyqlv+yry6sslgMbMbf895TTtuG/XQpLwlICTHtFYcM0W8FDaW2L/EuB1ifM6xG+m1A/fFtGoPc0ey9lsgBXOr4mbKzBadzdZgOl1VjlL/cAnwUw7tGul9zfPm1jc+1X/7kbHWqRaa3vYTvdk8o3QPMKuesU6x+x9x1kgKIwwp0+LuvKBLwzhbBeVCP18JASct/NBPpECPeIxZDHODdptndzPRaWRAmok8kLaTLlf1mDjNPMeN9cAxyXHcBoi/fsz4Pa9JCjf2FlreiVnjoi4VzjgfLqIQ/ZjsE8/Wt1Bh1HpXCvjw7KD6YY+LRFp1/uNHkDI7Tsr9CqQOAVlZY3DGpwEmOZUsd1oUOrR+lrGb78SZikOajNErulbWFiA/9jmbCD5qzgHUGmE/uxUaK2GEaT9D3WPGFRDczv8+UweHTsDS5lgdoNahUzMZ9FBOoLgbg3XPKwIxzlhOi5Li+nZjZA931/FstKw6SNVtgxE5wlI4bLyiFwyOX8flMG77pOj4WobQQYELscwsIa/nXGZRZYHk2iVU2mUP049olNTBtqpbMNkuX4VB0PZG4jIMPMsm6eCGS81ViRrW4ec3Z6bJqvaRVTb/dssrw2hrgNwfXe686AUSamO019iDtIDfD6O2h3M9EpdFJvoAHPngyTP09yCIJj1dwpCJf2NyuGtDRpnp0MMpkNLI6A0FRLCktdT3rAwyjdo/VI4TAEz8gWjma9OmSbeT/JKdemrW1D48KDpmTcni3IUZ9SPLSEY7zTfyJh28+hDVYbxbGSG4gkNKiOg2Npvn0oFqd6y/LGfdeDcz2a9u+XhQLsHhQSo8Hgdxrk5kS1SEc7onf8SfYM8Rrt6YruEOjYJcw57szxDoc2Z3Cux/xWr+pdzOM0vlQ3L5KVBh3gRfVBHKqeOB8nlH3OHgl4FxtO+WY8MlMCaggEVdBIAb/pjwHUi8Mu8W6dKANVRaE084/VUmtjfvaRhk1C0RjoI10CldhCbCcNvws8yOiCgxG9ou3X9vgWAZL8FquOaSd5SrfuxB9IcVKQxBIkogRw06ZV9jupdPioet2rjjTN/hyoWnGbJblWPsn8nGV/WzZ8B2iJChEym5mVrQBDZd/mA55e9ci8yOibUv5N7kOiYyH0iDc93Rh45t6KYhbWzk/Y4KwBHjKGKMMMB2l3mxUrxLFrk6CogWJCJ1FC2dX9Xj84IY7WbIH9dHgWej/vJVuFFq8Ym12rHgHw28YnJlhSGa6Y07taIjQ51qdn5YEsAPWxgl3FjFXRsVGskdTAC1lU37xmjWeLY3AX/ijDAhywaWNl4yYecndpYgKldv9067GxGArMWcAsJP4HW9UMjk2igJTTen4d0TjAWdv0tXfyFSPgbp7I6McyScuNZZfvicUMWflWm7bWseQJQ4hNd9Y3RniCFq/rELJWcX4lh
Which again, appears to be further cypher text, not sure what to use for the next key. NIGGER.
This is the WikiLeaks insurance file retard. Last time we had one decrypted it was millions of unredacted cables, the most important information in years. Somebody dropped a "key.png" and some information. See if you can figure it out
Why was last thread 404d?
Like I said I can crack this shit because I can recognize the patterns being drawn from the use of the same complications. Meaning the methods you showed results from have been seen before online, and they were used to map out a location on a map where naughty things were taking place
Things you don't want to be associated with
So as a heads up I am telling all Anons that this seems to be a pattern that is reoccurring related to the plotting of select locations to be targets that are basically attacked mysteriously
The last QR Coded puzzle was found on a school ticket window, and had a UVM Medical Records File linked to the Anonymous image on the QR Code.
The whole thing was segmented with a secondary code that came embedded inside of the first coded sequence, so as to deliver a second branch of the strand's movement through a couple of basic examinations I made. The secondary code was then spray painted on a wall and the photo posted with the tag on it lead to the same mapping of ciphers into a sort of roadmap of things that appeared to take place shortly afterwards.
This particular cipher led to the Sabine Pass event blowing the refinery there and then a second coded message set the targets in Spain at the refinery there.
So notorious and stealth, but at the same time elusive......take notice of your results and use multiple reviews of the ciphertext on brute force settings to try to work a secondary classic cryptogram out of a plaintext that comes out of them.
These always have another meaning is what I am saying.
I don't know how you get that result which is obviously wrong when you key length is neither 32 for 256 bits size
Glowniggers, JUST SHRINK GOVERNMENT AND BALANCE THE FUCKING BUDGET.
>GUISE IT IT TOTALLY HAPPENING
>IT IS CICADA ALL OVER AGAIN
>WE GOING TO BE A PART OF A SUPER DUPER SEKRIT SPY CLUB
Should i bash your in head with a brick or will you do it yourself?
why is any thread 404'd? because they don't they don't want you to see what was there; for whatever reason.
Can you post anything of results from his fantasy breakthrough?
I mean is there even a single piece of evidence that says "This is a Wikileaks file" anywhere or is this some other form of "Insurance" from someone totally different?
Snagged this off of infinity chan back in 2018, could never figure out what S9 was.
38ca0ca721d56718c18a42ab80647b994e933b7070a5dafcf06d185e23f0edba
archive.4plebs.org
Check if this has anything to do with it op
bump
Its the base64 encoded form of the key. 32 bytes. 8 bits per byte. 256 bits.
Hex form:
>228bfc85cdd10ec9d4ad0984e354cc31c75c1363ec4766d93ce1306cc70f837c
also 256 bits.
Both keys work if you specify the encoding m8.
Yeah true but isnt it just increasing curiosity? Its like there is a door and it says FUCK OFF, dont you just want to open it?
Some wannabe cicadia 3301 shit imo. Interesting nonetheless. Not even going to pretend I know what to do with said info tho
and trying to post the original key image consistently results in a connection error, while another image works. very odd.
Can you make a screenshot and post as image?
just get it from the original thread
>diagnosed and medicated
For what it's worth the 999 key or bump key first thing came to mind.
en.wikipedia.org
Old leaks with some hot kill lists from Homeland Security and a file titled SUMOP as in some operation......
Someone dropped the file a while ago and now they are dropping it again with their own PGP Key or some other mode of encrypting a random link
This is why nothing gets done
user ask yourself.....if it was that important than why go through the trouble of encrypting it if your intention was to tell everyone about it as "Insurance"?
Seems like "other than advertised" goods
So what if the garbled text posted with the key is not the message itself, but a hash of one of the insurance files?
I'm not super familiar with sha256, but it's the encryption Bitcoin uses. When you use a "bitcoin recovery service", instead of using your wallet.dat file you create a hash of that file with hash cat. This is useful if you are enlisting someone else's services to "crack" your bitcoin wallet, without giving them the whole wallet. If they have the right key/password, the hash will unlock. Then you know the key/password will work on the original file.
I might have some of the terminology wrong, but tl;dr:
Why not try the base64 key on some of the original insurance files?
jesus fucking christ, my goddamn browser was totally fucking borked on Yas Forums.org because the 4chanX script needed an update.
now...did anyone try the secure tripcode or filename/hash from the fucking Q post elsethread earlier?
What IV are you using?
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAACPSURBVDhPbY0LEoQwCEN7/0srYFMfKZnJkl/d9QTWWkUHM+/1JvgVHHjmXaNCvyLhPnE+wAfTQ3bN129gGk3wLnQfcsDLnen73+TVeZ/A5h8Lqac8wbxYbkPhpAnr9pf+4NLyiatrZnPKmOsWp1Bal3mCPu49JNXpDtknBI2YS0/5cSx5SeLkMi00L9z9el4IBmi013So4gAAAABJRU5ErkJggg==
original key.png encoded to base64, just reverse the encoding.
based american flag Q poster
16 null bytes (CyberChef default)
Yea that's why your result is poo
Fake and gay. Original post said the source was ASCII after decrypting AES256
filename hash does not work.
This is true, I have been on that thread with the devs who did it/helped
this
OP also suggested key was the bits encoded in the black/white cells but that was clearly not the case(at least for this layer) as the key for this layer ended up being the sha256sum of the image instead.
You've not produced anything of value and don't know what you're talking about, I'm done with you.