EveryoneIsOSS ID: 405f92 July 2, 2022, 1:58 p.m. No.24005   🗄️.is 🔗kun

>>24004

>This weekend workfag's are in the house crowd has been very receptive to the Tripcode "Q" isn't the Real Q sauce.

tend to agree with this

I have been here all morning, kek

EveryoneIsOSS ID: 405f92 July 2, 2022, 3:14 p.m. No.24025   🗄️.is 🔗kun   >>4029

and

not that it really matters

 

but is 'webmanon' faggot in current bread tubbaks?

 

because it really seems like tubbaks

EveryoneIsOSS ID: 405f92 July 2, 2022, 3:19 p.m. No.24028   🗄️.is 🔗kun   >>4030 >>4034

>>24024

>So the old known Q passwords still result in the same known trips...

okay I read this like 5 times and didnt understand what you were pointing out

>This PW ends in an exclamation point...

I see that

chek't

>Meaning the salt is the same as 2018...

wait

wait

wait

 

what the fuck?

the salt ROTATED when 8kun went live in 2019

 

everything pre-Nov 2019 salt rotation should beDIFFERENT NOW

 

your saying

that a now known password for one of Q's tripcode circa 2018 is RIGHT NOW resulting in the tripcode from 2018???

 

is that what I am reading?

EveryoneIsOSS ID: 405f92 July 2, 2022, 3:21 p.m. No.24032   🗄️.is 🔗kun   >>4038

>>24029

I'm picking up what your putting down

and I agree

 

tranime showed up during the great kitchen fire of red october

and fought on the side of patriots as far as I could tell

EveryoneIsOSS ID: 405f92 July 2, 2022, 3:23 p.m. No.24034   🗄️.is 🔗kun   >>4043 >>4049 >>4051 >>4094 >>4347 >>4509

>>24028

>everything pre-Nov 2019 salt rotation should be DIFFERENT NOW

>your saying

>that a now known password for one of Q's tripcodes circa 2018 is RIGHT NOW resulting in the tripcode from 2018???

 

>>24030

>Yes.

>sauce

 

uhhhhmmmmm anons

how the fuck is that possible

if the salt DID actually rotate in November 2019

EveryoneIsOSS ID: 405f92 July 2, 2022, 3:38 p.m. No.24052   🗄️.is 🔗kun   >>4055 >>4104

>>24049

>they know we know the canary is dead and that's all that matters.

5:5 on that

 

still curious about this post

 

this should be a dead canary

and salt has been rotated since it died

so it shouldt even exist in the ether anymore

 

>>23860

>>23860

>>23860

 

so how is THAT happening?

either someone has broken the salt crpytography so completely that they can reverse engineer the password required for any given tripcode, regardless of salt conditions

 

or there is a hard-coded bypass

EveryoneIsOSS ID: 405f92 July 2, 2022, 3:39 p.m. No.24053   🗄️.is 🔗kun

>>24051

>in other words, the site has been comped since day one. and q knew it from the start.

this makes the most sense to me

there is no such thing as a "trusted" website

EveryoneIsOSS ID: 405f92 July 2, 2022, 4:53 p.m. No.24102   🗄️.is 🔗kun

>>24084

>Means the person who posted had the password Q used

no

that is an old trip

its based on an OLD salt that has been rotated away from

the password Q used to generate that tripcode with the OLD salt would result in a NEW never-before-seen tripcode now that we have NEW salt

EveryoneIsOSS ID: 405f92 July 2, 2022, 4:56 p.m. No.24107   🗄️.is 🔗kun

>>24090

>Why would [site admin] hard-code an old Q trip that shouldn't even be possible since the salt rotation of 2019

 

it seems likely this 1 post in bread poster in our current bread isNOTJcrew

and thusly

likelyNOT8kun site admin(s)

and thusly

well there are not many options beyond that other than our favorite anon

EveryoneIsOSS ID: 405f92 July 2, 2022, 4:58 p.m. No.24113   🗄️.is 🔗kun

>>24094

>Did Ron actually rotate the salt, or did he just say he was going to rotate the salt?

Q got a new tripcode if I recall correctly

that can be checked easily in the drop archives

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:01 p.m. No.24115   🗄️.is 🔗kun   >>4124 >>4130

>>24096

>So are you saying someone did a hardcode for the Q post in here that has the old trip code?

 

correct

 

we are saying

 

Either:

 

  1. [someone] performed a hardcoded salt bypass tripcode post that displays an old Q tripcode

 

or

 

  1. [someone] brute forced the new salt (circa Nov 2019) in order to generate an old Q tripcode with the current salt conditions

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:08 p.m. No.24120   🗄️.is 🔗kun   >>4121 >>4124 >>4125

>>24096

>or someone has q's old password

we do anon

that is how we have been testing

 

anonHAS THE OLD PASSWORD THAT IS SUPPOSED TO GENERATE THAT TRIP

it doesnt anymore

 

see: >>24087

>Nope. I tested that. The salt was rotated in 2019.

>Old Q passwords do not result in old Q trips.

if that anon is still here

 

they can demonstrate it again

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:11 p.m. No.24123   🗄️.is 🔗kun   >>4136

>>24104

>Who ever it is seems to be giving us a clue as to what is going on

exactly so

we wouldnt be having this conversation

or discovering the Truth of this "feature"

if it were not for that post

 

we have been discussing it previously, yes

but its been just another spitball on the wall

 

this post requires explanation

and I think as we figure out the explanation

we will get our "proof" for exactly how the fuckery was performed

 

I could also be literally retarded

so there is that

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:13 p.m. No.24126   🗄️.is 🔗kun

>>24105

>Maybe CMZ is not a fan of Jim's LARP game.

it seems a distinct possibility

if anyone could have left themselves a backdoor into 8kun

its CM

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:19 p.m. No.24132   🗄️.is 🔗kun   >>4154

>>24112

> - mole in Jcrew exposing them

> - someone in Jcrew mocking us

> - CodeMonkey pissed off throwing us a bone

> - Its literally Q

 

those are all distinct possibilites

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:20 p.m. No.24133   🗄️.is 🔗kun   >>4160 >>4161

>>24117

you talking shit on numberfags bro?

kek gave you 17 in your post number

sit on time out and think about what you have said

and how it could affect the Q movement

dont you have better things you could be spending your time on?

 

Ohh fuck

I just became Jim

/sarc

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:27 p.m. No.24143   🗄️.is 🔗kun

>>24127

bahahahahahahha

they deleted/banned you for that one post?

had anyone even replied to it?

 

for fucks sake

over the fucking target

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:29 p.m. No.24152   🗄️.is 🔗kun   >>4174

>>24149

>Unless all Q trips are hard coded????

Unless all Q trips are hard coded????

>Unless all Q trips are hard coded????

Unless all Q trips are hard coded????

>Unless all Q trips are hard coded????

Unless all Q trips are hard coded????

 

 

my mind just became gravy

EveryoneIsOSS ID: 405f92 July 2, 2022, 5:32 p.m. No.24163   🗄️.is 🔗kun   >>4187

>>24130

>As well both are plausible, but option 1 is more likely than option 2. As option 1 is far more simple than option 2.

occums razor says you are 100% correct anon

EveryoneIsOSS ID: 405f92 July 2, 2022, 6 p.m. No.24228   🗄️.is 🔗kun   >>4232 >>4240

>>24221

>a different salt is used not no salt

okay

Ill conceed on that

yes

a different salt

specifically

an "insecure" salt

 

okay

getting deeper

 

what is the technical difference between "secure" salt and "insecure" salt

 

???

EveryoneIsOSS ID: 405f92 July 2, 2022, 6:03 p.m. No.24233   🗄️.is 🔗kun   >>4242

>>24224

>So the >>23860 is meaningless in regards to salt at this point.

 

kek

other than the fact they it got us to perform this little tripcode fest

but yeah

its not nearly as unique of a situation as orriginally considered

 

-anyone- with that list of publicly leaked passwords could have made that post

!!OWdeYcHrBQ ID: 405f92 July 2, 2022, 6:04 p.m. No.24236   🗄️.is 🔗kun   >>4239

>>24232

>secure == underthe possession of authorized users only.

what the fuck are you talking about

 

I can use the secure tripcode ##EveryoneIsOSS right now

its not under anyones possesion

EveryoneIsOSS ID: 405f92 July 2, 2022, 6:06 p.m. No.24241   🗄️.is 🔗kun

>>24226

>It kinda confirms that Q's password is hardcoded(only the single ! tripcode ones)and not[secure]salt dependent though

 

^^^

agreed at this point?

EveryoneIsOSS ID: 405f92 July 2, 2022, 6:14 p.m. No.24244   🗄️.is 🔗kun   >>4247 >>4274

>>24239

>plus you asked for the technical def. not the realistic state

 

I meant in the context of tripcode generation anon

 

insecure salt tripcode (#): do these change with salt rotation?

we have already tested with all the past single # Q passwords, looks like NO they do not change with salt rotations

 

secure salt tripcode (##): do these change with salt rotation?

well, a whole bunch of anons noticed their tripcodes change with that fucky situation on friday

 

but, something else happeneing on friday that correlated with the salt "rotation"

 

OSS noticed it

I am pretty sure 8bit noticed

 

EVERY SINGLE ANON on 8kun's ip hash changed when the "salt rotated" on friday

 

I didnt take screenshots and I am bummed I didnt

but

it looked like this

 

I had 127 posts in the /qr/ META before friday salt rotation

 

I had not noticed the salt rotation yet

I made a few more posts in /qr/ META and noticed that my UID had changed in the bread

I am like, what the fuck?

I have been posting in this bread for days

and now I have new UID?

what gives?

(this is on a hardline cleanet connection)

 

I made like 4-5 posts under the new UID

24 hours goes by

 

I go back into the /qr/ META on saturday

 

ALL MY NEW UID POSTS ARE NOW BACK TO MY OLD 127 POST UID

 

I now have 132 posts under my orriginal UID

 

the 5-7 posts that I made with the "new" UID in that bread during the salt rotation BECAME THE OLD UID after the salt "rotated back"

 

so

should EVERYONES IP hash change when salt rotates?

is that standard practice?

 

IP hashes are generated based on the salt?

-obv

and the IP hashes CHANGED when the salt rotated?

-obv (we witnessed it)

 

so

IP address hasing uses the secure salt that actually" rotates?

EveryoneIsOSS ID: 405f92 July 2, 2022, 6:29 p.m. No.24256   🗄️.is 🔗kun   >>4461 >>4463

>>24253

>Q making fun of us?

that aint making fun anon

 

3 solid connections

 

17 second video (kek)

posted @ 7:54

Q drop 754 is a SEC_TEST

 

no, the kicker, anon?

 

check the tripcode in use for drop #754

 

!UW.yye1fxo

!UW.yye1fxo

!UW.yye1fxo

 

....I dont care how retarded I sounds

thats dasting

EveryoneIsOSS ID: 405f92 July 2, 2022, 6:32 p.m. No.24259   🗄️.is 🔗kun

>>24254

>What if CM just used custom_tripcode to setup q's tripcode.

that really wouldnt be secu....

>then salt rotation wouldnt matter. wouldnt be very secure but it would work.

...right...

>Maybe q's password is very long

kek

then why have salt in the first place?

 

to make people FEEL confident based on a system that is not actually in use?

EveryoneIsOSS ID: 405f92 July 2, 2022, 6:53 p.m. No.24280   🗄️.is 🔗kun   >>4281 >>4288 >>4319

>>24267

>and if the salt is rotated

>(## + password) gives (!! and a different trip code) afterwards

exatly this

 

only ## generated !! trips and poster_id uses the secure_salt_trip

 

custom_tripcode based tripcode generation doesnt give a flying fuck about salt conditions

 

ergo

theonlyway to generate this!!Hs1Jq13jV6tripcode after the salt had been rotated is with custom_tripcode

 

(or brute force, but much less likely)

EveryoneIsOSS ID: 405f92 July 2, 2022, 7:06 p.m. No.24295   🗄️.is 🔗kun

>>24288

>but with the reverse of the salt after the initial fake Q's were posted, it is no longer worth considering.

agreed

 

the salt rotation is one thing

and honestly

Jcrew should have ran with it

reverting the salt BACK AGAIN is the most comp'd thing in the fucking world

EveryoneIsOSS ID: 405f92 July 2, 2022, 7:20 p.m. No.24303   🗄️.is 🔗kun   >>4306

>>24283

>Also in functions.php we can see that IP hashes are generated similarly to secure tripcodes.

thank you for tracking it ALL down

 

we confirmed poster_id used secure_salt_hashed

nice to also confirm the base IP hash is also generated with the secure_salt_hash

EveryoneIsOSS ID: 405f92 July 2, 2022, 7:42 p.m. No.24315   🗄️.is 🔗kun   >>4318 >>4332 >>4347 >>4509

>>23860

>Q !UW.yye1fxo - 9aa6f4 (1)

 

now that we have done the full round robin on this situation;

 

I am re-visiting this anon

clearly anon "anon" could have posted it

 

breaking it down:

 

its a reply to this text:

 

>Everything else is noise until a satisfactory explanation for how that happened

we need a satisfactory explaination

>that DOESN'T include the most obvious hardcoded fuckery.

meaning

we need to explain EVERY OTHER avenue possible

besides the obviously possible hardcoded exploit

>Don't hold you breath waiting for moar details about CM's nobody knows how he did it workaround for Q

true that

we couldnt it sauce it ourselves anyway that >was never mentioned in the drops before.

also true

everything we need is already in the drops

 

okay

so anon replys to that post

pretty fucking quickly (less than 3 minutes)

with NO TEXT

 

its literally an easter-egg post

and the easter-egg (once we figured it out) decoded (for lack of a better word) the anons post that it was a reply too

 

caused us to attempt to repeat what was accomplished in the easter-egg post

 

and we succefully did repeat it

 

and in so doing

not only did we "decode" the anon that was being replied too

 

we found theactual truthof the situation

 

that is some inception level easter-egg socratic methodism

 

and aHUGEamount of trust/faith that we would even find it

 

am I literally retarded here?

anyone else picking up what I am putting down?

EveryoneIsOSS ID: 405f92 July 2, 2022, 7:51 p.m. No.24320   🗄️.is 🔗kun   >>4324 >>4330 >>4347 >>4509

>>24317

>I got a LOT of legit question on the babyfist shit

not the typical hurr durr shit

 

more like

are you fucking serious?

prove it

>I post sauce

minutes of silence

 

they come back and actually ask questions about the sauce to try and fully understand what it shows

 

>asnwer technical questions about sauce

they come back still not quite understanding it with screencaps that they think refute the sauce

but not all hurr durr

like legitimate contextual refutation

post number wrong

timstamps dont line up

 

like

they dont WANT to believe

so they are trying to make sure the sauce is bad

 

>give further technical explanation about the sauce that clarifies their refutation

 

ohh fuck anon

looks like your right

got any more on that subject?

 

1,2,3,4,5,6 questions about all of the possible implication of what that sauce means now that it is confirmed true in their mind

 

I post the FULL babyfist bun

 

SHUTITDOWN.png

picrel

 

REEEEEEEEEEEEEEEEEEE

REEEEEEEEEEEEEEEE

like a godamned wiley coyote in there

 

and then

like it never even happened

onto the next bread

 

I think a solid bunch of anons digested the digs and saved them

EveryoneIsOSS ID: 405f92 July 2, 2022, 7:57 p.m. No.24323   🗄️.is 🔗kun   >>4327 >>4335

>>24319

>So who rotated the salt 3 hours prior to ##4954?

 

currently at the top of the brainstorming pile

 

Jim did it thinking it would lock Q out of posting with his secure_salt_trip##based password

 

Jim would rotate the salt without anyone noticing

kek

Q would no longer be able to post with !!Hs1Jq13jV6 using his ##password

Jim could post with !!Hs1Jq13jV6 using cutom_tripcode

 

thats my top line

but there are many other potential hypothesis

EveryoneIsOSS ID: 405f92 July 2, 2022, 8:13 p.m. No.24333   🗄️.is 🔗kun

>>24328

>the recent Jim video where he and others mused nastily on what to do to Fred B.....pretty dismal portrait being painted of Jim's morality

I think this vidya was a huge turning of the tide

left a horribly bad taste in a LOT of peoples mouth

 

hillariously

a large percentage of the current Q social media movement isnt really familiar with everything that has happened with Freddy and Jim

quite a few anon actually still have a fondness for the little cripple

I would count myself as one

 

and 99% of the larger 'Great Awakening' movement has no fucking idea who Freddy is

 

so, they have literally NO IDEA why Jim would have any grievances

 

they saw that

and were like

what the fuck?

$15k to take a cripple guy out on a boat and "take care of him" ???

 

Jim

that was dumb as fuck bro

EveryoneIsOSS ID: 405f92 July 2, 2022, 8:21 p.m. No.24336   🗄️.is 🔗kun   >>4338 >>4347 >>4509

>>24332

>How do you explain getting the same trip code as Q's last trip with a freshly rotated 3 hour salt?

its such a vanishingly small possibility

(brute force a brand new secure salt in 3 hours or less)

and now that we have discovered an "easy way" it could have been accomplished

...

ocams razor says it was the custom_tripcode method used to generate Q's trip then entire time Jim did it

 

>hivemind, many "synchronicities"

indeed anon

many such cases

 

before /hivemind/ was created

before I left after Jan 2021

I was fond of using the phrase

"the hive is alive"

when referring to synchronistic occurances on /qr/

happened so often

I used that phrase to name a series of meme caps that I would save as they happened

picrel

kek

 

I often wonder where the name hivemind was chosen from

strongly feel its another one of them synchonicities

to many, and too profound to mention at this point

>in the flow

absolutely this anon

'surfin

EveryoneIsOSS ID: 405f92 July 2, 2022, 8:45 p.m. No.24341   🗄️.is 🔗kun   >>4344 >>4346 >>4347 >>4509

>>24340

>salt, no matter which server it is on, is single-use when used correctly. secops 101

this

>you DO NOT save copies of the salt. ever. again, that is secops 101.

also this

 

I have not heard anyone attempt a good explaination (like it even matters, kek) for even HAVING the "old salt" to go back to

once a salt is burned

its done

finito

gone into the ether like so much dust in the wind

because, secops 101

 

going through your logic anon

once they realized what had happened

 

>2b) discard ALL hashes and start over, with a general announce.

is theONLYsecure option on the table

the fact that they took the dev instance and ported it over to the live as a clone of the salt is SO FUCKY that if they had -just done that- and not even faked a Q post

it would prove this place comp'd from the root

at least

this place would exist in a 100% security compromised state until they rotated all salt