Anonymous ID: 11500a Dec. 14, 2017, 8:11 p.m. No.183   🗄️.is 🔗kun   >>185 >>186 >>188 >>193 >>197 >>200 >>205 >>237

>>14

This Q is highly suspect until proven otherwise.

 

Single hash trips are INSECURE and COMPED with relative ease. All you need is to know the hash method and an offline brute force attack. It's OBVIOUS this is what was happening earlier today.

 

Q trip is almost certainly comped, both here and at 4.

 

Clowns have successfully torn the loaf into pieces and are scattering it to the wind.

Anonymous ID: 11500a Dec. 14, 2017, 8:13 p.m. No.189   🗄️.is 🔗kun

>>120

Last post is obviously COMPED Q.

 

We figured out DAYS ago that #FLYSIDFLY# was McStain.

Nothing new

Comped Q.

 

THIS IS NOT A GAME.

Anonymous ID: 11500a Dec. 14, 2017, 8:18 p.m. No.199   🗄️.is 🔗kun   >>203

Fuck me, XXX tubbaks is back, this loaf is doomed.

 

Good luck tonight anons. It's going to be a shilltastic time. Have fun with that. I'll keep digging on my own and check in later to see if you managed to sort it out.

Anonymous ID: 11500a Dec. 14, 2017, 9:29 p.m. No.411   🗄️.is 🔗kun   >>413 >>510

>>237

>Normal tripcodes are not secure, and can be cracked with relative ease.

 

i do this for a living

i do understand how hashes work

i also understand how psyop and social engineering work

simple Q trip is NOT secure and is highly suspect until proven otherwise. period.

Anonymous ID: 11500a Dec. 14, 2017, 9:37 p.m. No.426   🗄️.is 🔗kun

>>413

I agree.

I am pointing out that the so-called Q posts today on 8pol and 4 are highly suspect.

I am also pointing out that Q was not using a 200-bit entropy tripcode, Q was using a "normal" tripcode, which would be relatively easy to crack.

 

>A very simple and visible example of this is 4chan's "tripcodes," which can be easily brute-forced given a long enough time (weeks to years on a single machine) and a powerful enough machine (or botnet, better yet) even if nothing about the password is known, characters in the password are chosen from a full range of ASCII, kana, and Kanji characters, characters in the code are case-sensitive alpha-numeric ASCII, and the code is 15 characters long. Here, the actual databases were not compromised, because no databases are actually kept (but the "hash," by which I mean the tripcode itself, is publicly displayed in that post), but the hashing function was discovered pretty easily anyway from ripped Yotsuba coding.

 

The ease of cracking a normal tripcode is well documented. Anyone saying it's not is lying or very badly misinformed.

 

Today's Q posts are suspect until proven otherwise.