Re: VMs: Word Endings

["Jeff" <jeff@xxxxxxxxxxxxxxxxxxxxxx>]

Don't I always share? :-)


----- Original Message -----
From: "GC" <glenclaston@xxxxxxxxxxx>
To: <vms-list@xxxxxxxxxxx>
Sent: 13 July 2003 02:26
Subject: RE: VMs: Word Endings


> Jeff wrote:
> >
> > In my opinion the glyphs match in pairs. It is the pairing that
determines
> > the plaintext character. It is a chain of pairs. ac could equal e AND vb
> > could equal e depending upon where they were mapped. There are x number
of
> > glyph pairs where x = the letters of the plaintext alphabet. a table is
> > constructed that runs first row a..z next row b..za next row
> > c..zab so each
> > column and row have all letters of the alphabet in offset sequences. It
is
> > the reverse of the pair compression cipher. The words are not
> > compressed but
> > maintain the same length with the first word having one extra letter to
> > start the sequence. All the encryptor has to do is find any
> > position in the
> > grid with the first plaintext character. Then lookup the row and column
> > glyphs for that character. The glyphs are written and the second glyph
is
> > used to indicate the next column or row to use to find the next
plaintext
> > character. The glyph that intersects at this position is then
> > written to the
> > cipher and becomes the indicator for the next column or row to search
for
> > the next plain text character and so on and so forth. Anyone that
> > wants any
> > extra information on this idea then let me know.
> >
> > I haven't found exactly the right order for the glyphs along the
> > axes but I
> > will post any advances asap.
>
> 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