It's incredibly hard to reverse engineer what password will generate what hash, even if you have direct access to the salt file.

Two real options here: either the site admin set aside a special salt file specifically for Q's password while changing all the others (this sounds like something they would try to do) and whoever posted knows Q's original password (the one he was using back in 2020)

or

Someone with access to the new salt file has reverse-engineered the salt to figure out what password will produce Q's tripcode when paired with the new salt file. Because of the salt rotation, this should now be a completely random string of characters with no relation to Q's old password.

In both of these cases, hacking the password would be extraordinarily difficult, but not impossible.

The first scenario would be far easier for someone to hack, since they'd be looking for a password made by a person instead of something random, and Q has used phrases for passwords in the past.

To reverse engineer a new salt file to produce a specific random hash matching Q's trip code and to do it blind with no common phrases to start with would be orders of magnitude more difficult.

Because of this, whether or not this is Q, the more likely scenario is that the site admin locked in Q's salt file to preserve it.

At any rate, 48 hour rule should be in effect. Real Q always verifies when reestablishing comms.

I'm assuming the BO/Admin excluded Q from the salt rotation. When 8kun went operational, CM contacted Q for guidance on salt rotation and Q asked that it be postponed for OPSEC reasons...

ArchiveAnon*** Forwarded from Praying Medic