>>6822193

Find and Download insurance.aes

Decrypt it in linux terminal using the following command:

openssl enc -aes-256-cbc -d -in insurance.aes -out [yourefilenamehere] -k 'ONION'

You will get a successful decryption.

The header of the file will read __SALTED which means it's still encrypted. You can successfully decrypt the created file again, and again, and again forever.

The same is true for -k "USE" and -k "ROUTER"

The first insurance.aes when decrypted does not produce any usable data.

I believe it's a tool to portray that onion routing (TOR) is valuable and necessary in this process of protecting against censorship and distributing the ifile data.

This file being decrypted in this manner is as old as 11/2016.

There's chat logs of people discovering this around that time.

Here's the thing. You ask for SAUCE?

You can find and do it yourself. The proof is your own to make.

the sha256 hash of insurance.aes should be

15bac5e815a38a998f4705945bd41975b736e7c723cfe851b9ed0e50c49316b4

>>6822378

The context of the repost was that the op notables were discussing using tor to search keywords provided by Q to "find the copies" and "open source."

I was simply adding context from JA, whom I think we all know is embroiled in the big picture here.

It's beyond any doubt that one of JA's insurance files has been decrypted (beyond the one containing diplomatic cables that he released himself at an interview).

That file is insurance.aes with sha256 of

15bac5e815a38a998f4705945bd41975b736e7c723cfe851b9ed0e50c49316b4

It can be decrypted using keyphrases

"USE"

"ONION"

"ROUTER"

This was determined in the early days through the use of a dictionary attack on the files.

JA would assume all of his files are subject to this simple low brow attack, and incorporated it in his means of spreading info.

And that info is as such:

Use Tor.

Why? for privacy, protection from censorship, and may more having to do with Q and the insurance files.

>>6822407

You don't think that its relevant when anons are mulling using tor to search Q keywords?

Stop being so stubborn.

>>6822434

No shit nigger.

Supporting context was all that was being provided.

I do, however, find it funny that the best deepweb tor search engine is called notevil

http://hss3uro2hsxfogfq.onion/

>>6822498

-Provided by me, to provide context for the anons discussing searching tor

>"however = but,"

please allow me to change that sentence:

"Find it funny that the best deep web tor search engine is called not evil"

>The Meat = http://hss3uro2hsxfogfq.onion/

Now the almonds are activating.

One person can't do everything here. That's how people get Arkanicided.

>ex:Danny Casolaro

Part of what makes me think JA is tightly related to whitehats running Q et. al. is that in the blockchain, uploaded 10/21/2016, there is an unclaimed pgp message. In that message is a base64 encoded string that decodes to "Consensus Omnium" and some numbers.

What do you think consensus omnium means?

What do you think the Q project is meant to do?

Why would it be valuable to have a pgp message immutably anchored in time in the btc blockchain?

Speculation, but there's a bigger story forming here and I was intrigued by the anons willing to scour tor for more info.

Hence the "why"

The full pgp message is below:

—–BEGIN PGP SIGNED MESSAGE—–

Hash: SHA512

Fools rush in where angels fear to tread.

46aecab3df447edd6539888b50dd8996e2d4da782d3451c5f4764d8737e4cd533020f424d93f7ce97f95102ba986e4b5b9eb549d32fb8f85ea79edf35379eb68

c071aa9f683b497b68cc5958c2acef8c26a2f36fe387887b5f68cf5ef05203b62858e937b0a7b8e5d938da85d877fadb245c740c6853b27f93f9a0cb84500101

Q09OU0VOU1VTIE9NTklVTSAvLyAzNjQxNCA4MTQgODE0IDQ0OTMwIDYgNiAwMDAwIDAwMDAK

—–BEGIN PGP SIGNATURE—–

iQIcBAEBCgAGBQJYCbq7AAoJEM3lTKOOnkanngkP/i39oLudJmpJZSQIUAzAuVLr 2lY212qOKoNtHrnbBf2AaFqYUU0+Ln1799gxFvEQfL8GPiGlcBIVgh8G1Q1roFMC Ll0W6g+dFwokMMG5HH7guVuMRQ/HaLh3Mj67p4f5SIGngWVmuGzG2if8mxFrHhjy 20AsRAU/5jVXqkHR/d+1V9xwLQvawxDnJU/vMzA3oKb3ObLfgS+oj+AuybVeI93I 0iMfGug95KIvVImAL5YYzWMm3gHG7UDy1wI9VOVP7RfIImePLJTzK0/P23wATGse 1aQMKx6axBvuqAjf4ZL8cyXn1yZnwM/FhE1MvrsAx2G6X3E4+PWgWjJEK0JWPOT8 vcVkZgSAgLACiiMbfY2ZBX2jCK42nqttn0zofYhyRdU0wUGRalCDRfaof4TW+XkN 1PtRbxCnxgv1PSqnI7dizwoQO6nxWRW/ZzBRamOKTeu9G4pSlCgCdZsUEgHFlvKL 9F2wH6ATohpbdQAkHuCLxq1L

gpg: Signature made Fri 21 Oct 2016 02:50:35 AM EDT using RSA key ID 8E9E46A7

gpg: WARNING: signature digest conflict in message

gpg: Can't check signature: general error

$ echo Q09OU0VOU1VTIE9NTklVTSAvLyAzNjQxNCA4MTQgODE0IDQ0OTMwIDYgNiAwMDAwIDAwMDAK | base64 -d

CONSENSUS OMNIUM // 36414 814 814 44930 6 6 0000 0000

I will also note that the base64 string starts with Q and ends with DAK. Maybe the padded numbers after "consensus omnium" are there to generate that coincidence…