Re: re:Algorithm

From: Michael Jørgensen (ingen_at_ukendt.dk)
Date: 12/22/04 

Date: Wed, 22 Dec 2004 09:40:27 +0100

"Rayman" <that_guy_that_was@hotmail-dot-com.no-spam.invalid> wrote in
message news:41c8ea60$1_1@Usenet.com...
> Lol you don't get to see my source code for 2 reasons.
>
> 1: This is cryptography. If were to try to complete the crackme by
> reviewing the source code, then I would have posted it in a cracking
> section.

No, this is snake oil. Cryptography is all about analyzing and reviewing the
algorithms. When you don't post your algorithm, then how are you going to
convince people that the algorithm is great?

> 2: I really would hate to see someone take my source code and slap
> their name on it and talk about how they came up with such a great
> algorithm.

Well, I hardly think so.

-Michael.

Relevant Pages

  • Re: Blowfish Sign Extension implementation risk
    ... > Tom St Denis wrote: ... >> the algorithm correctly in the first place is the better course of action. ... mainstream, was published with C source code (again, see Dr. Dobbs, ... Applied Cryptography, etc.). ...
    (sci.crypt)
  • Re: re:Algorithm
    ... Cryptography is all about analyzing and reviewing the ... When you don't post your algorithm, then how are you going to ... Wem das nicht ...
    (sci.crypt)
  • Re: Blowfish Sign Extension implementation risk
    ... > cryptography books, by Bruce. ... I definitely didn't use his source code ... > algorithm description, since the algorithm, as it is available to the ... > mainstream, was published with C source code (again, see Dr. Dobbs, ...
    (sci.crypt)
  • Re: Algorithm
    ... >1: This is cryptography. ... If were to try to complete the crackme by ... >reviewing the source code, then I would have posted it in a cracking ...
    (sci.crypt)
  • re:Algorithm
    ... Lol you don't get to see my source code for 2 reasons. ... If were to try to complete the crackme by ... reviewing the source code, then I would have posted it in a cracking ... I posted it to see if anyone could crack my algorithm with ease. ...
    (sci.crypt)