Re: The crazy encryption madmans codebook

<jt64@xxxxxxxx> wrote in message
news:1172882676.173526.142310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The only thing i do not follow is why the word *telephone* can not be
encoded to any word in the database.
Why would it not be possible, the offset number is just an integer
dependent on former decoded text,
used to find the right value.

Because k*i mod x is biased when x is not prime, hence the short loop
discussion previously. This is where the i=2, x=10 came in in the
explaination,

2*1 mod 10 = 2
2*2 mod 10 = 4
2*3 mod 10 = 8
2*4 mod 10 = 6
2*5 mod 10 = 2
2*6 mod 10 = 4
2*7 mod 10 = 8
2*8 mod 10 = 6
2*9 mod 10 = 2
2*10 mod 10 = 4
it keeps looping.

Since 1, 3, 5, 7, and 9 never appear the resulting value is clearly biased.

This is an assymetric crypto.

Not in any way shape or form is this assymmetric.

And for how to actually create the offset number i just throw forward
a fast idea, of course much more could be found using and oneway
encoding algorithm or hash over some chosen letter from the earlier
decoded plaintext.

That would suffer the same bias problem. And still would not address the key
space issue, in order to approach the capability of a 128-bit cipher block
would require 5 000 000 000 000 000 000 000 000 petabytes of storage, and
that assumes you use every possible 16-byte code instead of phrases which
will be enormously longer requiring much more space.

Maybe you did agree about telephone would be possible to encode to any
madman valure in the database and did disagree about something else,
or i just missunderstod you.

I think you're not understanding a large portion of what I'm saying.
Joe


.

Relevant Pages

  • Re: The crazy encryption madmans codebook
    ... the actual identifier in the database '12288. ... Just note that if offset multiplies to 0 then 0+12288=12288 it is the ... plaintext sentence you will get another offset. ... All you're doing is attempting to build a not very good chaining mode. ...
    (sci.crypt)
  • Re: The crazy encryption madmans codebook
    ... I do not see how *telephone* always encodes to anything particular ... the actual identifier in the database '12288. ... plaintext sentence you will get another offset. ... All you're doing is attempting to build a not very good chaining mode. ...
    (sci.crypt)
  • Re: The crazy encryption madmans codebook
    ... encoded to any word in the database. ... Why would it not be possible, the offset number is just an integer ... where each entry have an index, realworld word or phrase and a madman ... would call *offset keys* an offset key is used to encode *one and just ...
    (sci.crypt)
  • Re: Array contains too much data
    ... > taking very long for perl to parse the data, assemble it into html and then ... > The database now at 1000 entires it takes very long to essemble and print to ... Read up on the CGI module. ... and next page (if the current request is for offset 90 with a page_size ...
    (comp.lang.perl.misc)
  • Re: The crazy encryption madmans codebook
    ... the actual identifier in the database '12288. ... telephone=a bad smell' ... plaintext sentence you will get another offset. ... All you're doing is attempting to build a not very good chaining mode. ...
    (sci.crypt)