>>222732

Need to use a trip hashing function not based on DES as it’s been deprecated for longer than many of you all here have been alive.

>>222738

It’s better than the status quo - and will last longer before being comp’d, but given the obvious capabilities of our adversary, Upgrading to a better hashing function is really the correct thing. Maybe a ### extra secure trip?

>>222780

Not the board, just Q’s trips.

>>222799

That there is the issue. The hashing function is based on DES which only had a 56 bit key. Upshot is you can make the password as long as you want, but only the first 9 or so characters matter.

>>222825

You don’t have to decrypt the password, but yes, you can brute force a 56 but key with not much money spent with AWS to rent a bunch of machines to do it in parallel.

>>222841

This, this, and moar this^^^^

>>222856

A byte is 8 bits, but in terms of the “alpahabet” you can type trips in, it works out to ~ 6.2 bits per tripcode char

>>222807

>(You)

After looking at the php manual, picking a 16 char random secret board salt and prefixing that salt with $6$ will use a much stronger and longer tripcode. Can problably go with sha256 (using $5$ as the salt prefix) without significant loss to security. Even better is to use hash_pbkdf2 function to generate the tripcode.

>>222910

Yup

>>223027

Thinking that perhaps we should do these for the other major players to make it more consumable by normies, media, et al

>>223112

He’s an admin. See code monkey at the bottom of every page here? That’s him.

>>223107

Beat it FBI instigating faggot

>>223122

Think about this in IRL terms: someone sends you a letter snail makl without a return address. They can reach you but not vice versa.