Re: potential break or real break?
- From: rossum <rossum48@xxxxxxxxxxxx>
- Date: Sat, 03 Feb 2007 01:35:06 +0000
On 2 Feb 2007 08:17:22 -0800, jt64@xxxxxxxx wrote:
At least i think this is true for let us say a 256 bit key and a 256If your key is 256 bits long, then your algorithm can only produce
byte permutation like my simplistic cipher STREAMBUDDY, i don't think
it is a stream cipher it is a PNG based on "nonereversible/hard to
reverse" byte walks, creating two stream that is downmixed by XOR into
one stream, and then further obfuscated by XOR with and older round of
the combinatorial XOR shuffles.
2^256 different keystreams. If it produced more than 2^256 then the
algorithm would not be reversible and it would not work correctly as a
This allows an attacker to try every possible key, generating every
possible keystream and seeing what sort of plaintext results. A
simple statistical analysis of character frequencies will tell when an
interesting decryption is found. That is a brute force attack, and
every cypher with a fixed size key is vulnerable to it, no matter how
the keystream is generated.
OTP is not vulnerable because the key (not the keystream) is as long
as the plaintext so a brute force attack just produces all possible
plaintexts with that length, from "aaa ... aaa" to "zzz ... zzz", with
no way for the attacker to tell which message is the correct one.
- Prev by Date: Re: potential break or real break?
- Next by Date: Re: definition of statistical test for randomness
- Previous by thread: Re: potential break or real break?
- Next by thread: Re: potential break or real break?