Not quite got the point

OriginalGriff

Commit strip OTD: SHA1 Collision[^] Oh dear, oh dear, oh dear ...

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

Kornfeld Eliyahu Peter

:laugh: :laugh: :laugh: :laugh: :laugh: At this very moment I'm writing code, that uses MD5 (as request from 3rd party) to communicate secret info...

Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.

dan sh

I also did that once, nobody liked it. Here is the method I used:

public string SendSecretInfo(){
return "MD5 (add salt to taste)";
}

"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[^]

Lost User

I'm having breakfast just now. Shall I look for the secret decoder ring in the cereal box?

The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.

Sander Rossel

So tell us the secret info. We'll find out if you don't tell us anyway ;p

Best, Sander arrgh.js - Bringing LINQ to JavaScript SQL Server for C# Developers Succinctly Object-Oriented Programming in C# Succinctly

megaadam

If your hash keys are longer than 32 bits you obviously don't care about performance.

... such stuff as dreams are made on

OriginalGriff

64 bit machine: 32bit hashes just waste memory accesses! :laugh:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

megaadam

So, Mr. Fancy-Pants has got one of those modern PCs. I bet it is portable as well!

... such stuff as dreams are made on

OriginalGriff

Nah, it don't 'ave no 'andle. The WookieTab is though. :-D

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...

User 12831244

ROT13 is enough for anybody :-)

Mark_Wallace

Well, mine has sixty-odd thousand ports! So there!

I wanna be a eunuchs developer! Pass me a bread knife!

PIEBALDconsult

I like GUIDs as IDs. GUIDs are 128 bits. With a 128-bit hash algorithm, I can make GUIDs from whatever arbitrary (string) values I may have (not user input or file content). And if I can do that within the database (SQL Server), then so much the better. Does SQL Server support any unbroken 128-bit hash algorithms? CAST(HASHBYTES('MD5',@Value) AS UNIQUEIDENTIFIER) Or, would prefer that I generate a 256-bit hash and throw out half the bits? How is that any better?