Re: Enig4



"crypticator" <crypticator@xxxxxxxxx> wrote in message
news:1138548962.343179.282310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi there ...
>
> here is a link to an encryption (sources and binairies ) program I'
> devised ...
> take it as my new year present to you ...
>
> http://www.ccc.ma/sw/enig4/

It is far better to provide an algorithm than an implementation. By far
better I mean, 99% of the time nobody will look at an implementation.

With that said, since the code is fairly self-obvious, I'm feeling generous:
I'm only going to deal with key generation and encryption, decryption should
be completely obvious from there

Keys are of a non-obvious type, they are {CTE = permutations of 0...16, CN =
64-bits}, this may make things difficult for actual use.

Encryption, this is an 8-bit feedback stream cipher I'll treat it as such.
For anyone attempting to follow along encryption begins at line 103

The biggest initial problem I see is that a chosen plaintext very quickly
spits out all the key material, and making correlations between them appears
to be easily possible within 16 bytes. Extrapolating this, assuming the
input is unknown ASCII text it should be possible to recover the entire
initial state within 64KBytes, with known plaintext I suspect the attack can
be easily reduced to 1KB. Once the entire state is known it is easily
possible to run the process backwards, as demonstrated by the decryptor.

I'd say that where the process falls apart is when you start splitting up
the byte for processing. In doing so you end up revealing more about your
state than I think you realized. My first suggestion is to have a look at
RC4, a lot of your ideas are very similar. It will show you some very
important design flaws, and should prove interesting for your situation on
how to begin to make it secure.

Also since you seem to be interested in feedback stream ciphers, I'd suggest
looking at how CCM and GSM both work, along with CBC and OFB. In particular
the proofs of security around them should be quite enlightening as to how to
do things securely.

It's not bad for a first public attempt. I think my personal first public
attempt lasted the couple of hours it took someone to make sense of what I
wrote. I do like though that you are experimenting in an area that is little
researched in the public arena, and I would like to see something very
interesting come of it. To that end I suggest you have a look at the Wide
Trail Strategy (Daemon and Rijmen both do a lot of work in this area) I
think adopting the techniques will make the path substantially easier for
you, especially if you examine the successes and failure of Panama.
Joe


.



Relevant Pages

  • Re: Unbreakable Encryption ? Scenarios - What encryption method would be best?
    ... DES is a well-known algorithm so there are good reasons to have a good ... > risk it by storing one of the best possible passwords (or encryption ... > Ok lets say there will be a secure channel but it will happen only ... > because the decrypting method yielded a plain text message and vice ...
    (sci.crypt)
  • Re: [fw-wiz] Re: Firewalls breaking stuff: [Was re: fwtk]
    ... > access to the mail server's private keys and thus the monitor can follow the ... > in a way that's more secure rather than less secure. ... for service level encryption versus VPN access. ... >> reducing bugs reduces the number of sever bugs. ...
    (Firewall-Wizards)
  • Re: Best secure surfing solution
    ... I have set up a service with companies providing secure web ... the product would have to install a keylogger. ... If we caught anyone in> IS or elsewhere in our company sniffing our communications, even if they> were encrypted, they'd get laid off or, at least, suspended. ... If e-mails are sensitive then> the sender should be using encryption. ...
    (sci.crypt)
  • Re: Best secure surfing solution
    ... I have set up a service with companies providing secure web ... the product would have to install a keylogger. ... If we caught anyone in> IS or elsewhere in our company sniffing our communications, even if they> were encrypted, they'd get laid off or, at least, suspended. ... If e-mails are sensitive then> the sender should be using encryption. ...
    (alt.computer.security)
  • Re: Symmetric encryption algorithm with group like properties
    ... >> Solutions that exist today are not as secure as they can be. ... I wouldn't expect more than PGP / GPG type encryption, ... > versions - with the key, protected by RSA encryption under a RSA public key ... > Alice needs a secure decryption mechanism to read her emails, ...
    (sci.crypt)