Re: Writing spaghetti code for obfuscation/encryption


Kevin G. Rhoads wrote:
> In any case, cryptographic security is NOT achieved by hiding the algorithm, but
> by proper use of a proven, tested strong algorithm and CORRECT KEY MANAGEMENT, the latter
> of which is easy to get wrong.
>
> Are you really sure you need to waste lots of time re-inventing wheels, and are you
> sure you want to start with a square one?

I don't mind using a good algorithm. I'd like to try ECC, actually.
But the actual handling of the key-check result needs to be hidden
and/or in some way made more difficult to find/remove/modify.

.

Relevant Pages

  • Re: Library for Mocking
    ... One of the advantages of a recording mode for mocks is that you can give ... good algorithm and can check that the new algorithm exactly matches the ... because the recorder wont return the proper values). ...
    (comp.lang.ruby)
  • Thanks for the responces.. another question
    ... I see it uses either Rijndael, Twofish, ... or Blowfish. ... Any algorithm better than the other? ... Also what is a proper ...
    (sci.crypt)
  • Re: Surrogate factoring, corrected algorithm
    ... Tim Peters wrote: ... I get a mere 24960 gcd trials. ... > some j, so at least one of {proof, algorithm, implementation} is wrong. ... I never saw a proof of the claim that one of the GCD's must be a proper ...
    (sci.crypt)
  • Re: Surrogate factoring, corrected algorithm
    ... Tim Peters wrote: ... I get a mere 24960 gcd trials. ... > some j, so at least one of {proof, algorithm, implementation} is wrong. ... I never saw a proof of the claim that one of the GCD's must be a proper ...
    (sci.math)
  • Re: Secure Empty Trash?
    ... but the most determined people from recovering anything. ... concerned about hiding something from law enforcement, ... 35-pass algorithm, but I'm not concerned. ...
    (comp.sys.mac.system)