[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: VMs: Word Endings
Jeff,
This is exactly as I described it, an autokey using a vig-type table.
Continue this for about 2,000 characters, and you can't fail to see the
'signature' or 'footprint' this system leaves in its wake. You CANNOT
produce line after line of VMS text using this system alone, and you can't
mask it's signature.
I am reminded of Jim Reed's findings in the Book of Soyga, where the
character's interpretation was dependent on characters placed at specific
points around the character to be written. To me this was essentially an
'autokey' text that lacked anything other than a keystring initial input.
Without any informational input, the available pages exhibited rather
flatline stats, only varying in a narrow 3-4 percentile range, if memory
serves. An internally dependent text such as Soyga provides a glimpse at
how such a system would vary language statistics when used to encrypt. The
answer - not much, by only a narrow percentile. If someone has a different
perception of this, please don't hesitate to make that known.
GC
> -----Original Message-----
> From: owner-vms-list@xxxxxxxxxxx [mailto:owner-vms-list@xxxxxxxxxxx]On
> Behalf Of Jeff
> Sent: Saturday, July 12, 2003 10:19 PM
> To: vms-list@xxxxxxxxxxx
> Subject: Re: VMs: Word Endings
>
>
> I have just looked up Vigenere tableau and see what you mean. This method
> however does not need the plain text cipher. It is a variation that can
> decode itself using letter pair chains. It basically moves around
> the table
> depending upon which cipher text character you last wrote. So if my table
> was:
>
> ABCDEFGH
> BCDEFGHA
> CDEFGHAB
> DEFGHABC
> EFGHABCD
> FGHABCDE
> GHABCDEF
> HABCDEFG
>
> And my indexes were ABCDEFGH Along the top
> And HGFEDCBA down the side (backwards alphabet)
> And the text I wanted to endcode was BAD CAD:
>
> I would find the letter B within the grid. Then I would find the
> cipher text
> characters for the column and row that the B was in. I would write these
> column first then row. so if B was in column C and row H I would write CH.
> Then I would look along row H for the letter A in bad. This is in column B
> so I write B giving me CHB. I now find D in column B. This is row C so I
> write C giving me CHBC. Now I have to write a space. Unless I want to add
> confusion, but why would I with this method? Now I find C in row
> C. This is
> in column A so I write A giving me CHBC A. I then find A in column A. This
> is in row A so I write A giving me CHBC AA. Lastly I find D in row A. This
> is in column D so I write D giving the final cipher CHBC AAD.
>
> If I had chosen any other starting position the pattern would have been
> radically different. Same plain text.
>
> Decoding is childs play. Each character pair maps to one and only
> one plain
> text character. Yet each plain text character maps to x number of cipher
> pairs.
>
> >
> > Correct me anyone, if you think I'm wrong, but what Jeff is describing
> here
> > is a first-character-initiated (non-keystring) auto-keyed look up table
> > constructed from a standard Vigenere tableau. Before you get
> too excited
> > about this idea Jeff, I suggest you enact your ideas on a standard
> construct
> > and view the results. I'm not certain if I ever checked for this in the
> > past, but I'm certain that auto-key cannot be responsible for
> the VMS text
> > statistics. Auto-key leaves a signature that I don't see present in the
> > VMS. Of course, I've been wrong before, will be wrong again,
> and oftimes
> > rejoice in my own dim light. Google auto-key cipher, and find out about
> > what you're testing.... and keep us informed on your
> discoveries, always!
> >
> > GC
> >
> > ______________________________________________________________________
> > To unsubscribe, send mail to majordomo@xxxxxxxxxxx with a body saying:
> > unsubscribe vms-list
> >
>
> ______________________________________________________________________
> To unsubscribe, send mail to majordomo@xxxxxxxxxxx with a body saying:
> unsubscribe vms-list
______________________________________________________________________
To unsubscribe, send mail to majordomo@xxxxxxxxxxx with a body saying:
unsubscribe vms-list