Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Tripcodes

Name: Anonymous 2008-08-05 20:12

/prog/, why has no-one found a way to directly find a tripcode?
Explain.

Name: Anonymous 2008-08-05 20:13

Name: Anonymous 2008-08-05 21:23

I'm seeing RAINBOWS in >>1's future

Name: Anonymous 2008-08-05 21:57

>>3
What are RAINBOWS?

Name: Anonymous 2008-08-05 22:15

>>4
Rainbow tables

Name: Anonymous 2008-08-05 22:25

>>5
DON'T HELP HIM!!!

Name: Anonymous 2008-08-05 22:41

>>5
Ah.
*googles*
I.. think I understand. Is this what tripper+ and the like use already?

Name: Anonymous 2008-08-05 22:48

While we're on the subject, can anyone explain why tripcodes are implemented so oddly? Why not just use a hash algorithm? They'd be long, but much more secure.

Name: Anonymous 2008-08-05 22:54

>>7
oh silly me, rainbow tables must be huge, right?
one could never fit into the 100kb of tripper+

Name: Anonymous 2008-08-05 23:02

>>9
so where might I acquire some of these rainbow tables, /prog/?

Name: Anonymous 2008-08-05 23:06

>>8
Why not just use a hash algorithm?
...

Name: Anonymous 2008-08-05 23:38

>>11
What's with the ellipses? The tripcode algorithm converts text to Shift JIS, replace characters with HTML strings, generates a salt, then uses crypt().

Maybe I should have written "cryptographically secure hash algorithm," like MD5 or SHA-1.

Name: Anonymous 2008-08-06 1:38

>>12
The ellipses indicate that I couldn't find words to respond to your statement.

Name: Anonymous 2008-08-06 2:27

its cuz u cant decode it cuz its a hash and its lossy so like theres collisisons read wikipeida you fucknig moron

Name: Anonymous 2008-08-06 3:19

>>1
because it's very difficult.

Name: Anonymous 2008-08-06 3:56

>>1
It is NP-Complete

Name: Anonymous 2008-08-06 4:01

>>12
crypt 3 is cryptographically secure hash algorithm.
just as secure as sha1 will be in 20 years.

...

Name: Anonymous 2008-08-06 4:34

>>1
tripcodes in a nutshell
(I am not a native English speaker, so forgive me if my explanation is not very clear)

There is a key (moot#faggot <- this is the key), and a buffer filled with initial constant value, same for each tripcode.
Each step of algorithm takes buffer, and modifies in a way that is dependent on key. This modification is pretty simple and reversible. Knowing contents of buffer before and after modification you can find key; knowing key and contents of buffer after modification you can find contents of buffer before modification. IIRC crypt(3) consists of 12 steps. The resulting buffer is your tripcode (!Εр8рui8Vw2).

Imagine crypt has only one step.
Then, as an attacker, you know contents of buffer before and after modification (Εр8рui8Vw2 and a known constant). You can easily find key and break tripcode.

Imagine crypt has two steps. You know resulting buffer, and initial buffer; you don't know key and contents of buffer between steps 1 and 2. To find key you need either initial buffer and buffer between steps 1 and 2, or resulting buffer and buffer between steps 1 and 2. To find contents of buffer between steps 1 and 2 you can either use key and initial buffer, or use key and resulting buffer. So you have to iterate through all possible contents of buffer between steps 1 and 2, and to see if you can find key for any of them.

With 12 steps and 11 unknown buffers this becomes too difficult and people just iterate through all possible values of key to see if they can get resulting buffer from initial.

Name: Anonymous 2008-08-06 10:04

>>18
Someone didn't pass his Cryptography 101.

Name: Anonymous 2008-08-06 11:13

>>16
Ah, I see. I recognize that term, thank you /prog/anon.

Name: !BkkrYWtNxQ 2010-05-02 11:05

How about I test a tripcode here

Name: !TOFgeH5H0A 2010-05-02 11:06

uhh

Name: !nZPM76YHww!HkFB8TVwKNwjx98 2010-05-02 11:06

hmm

Name: !GRwXD53RvE 2010-05-02 11:07

damn

Name: Anonymous 2010-12-21 0:32


Don't change these.
Name: Email:
Entire Thread Thread List