Re: Seriation

Stefan Claas wrote:

$ echo -n 'Hello sci.crypt! :-)' | xxd -ps | dkhf
48656C6C6F207363
692E637279707421
203A
2D29
 
$ echo -n 'Hello sci.crypt! :-)' | xxd -ps | dkhf | seriation
46 89 62 5E 66 C3 67 C2 67 F9 27 00 77 34 62 31
22 0D 32 A9
 
$ dokahex
Tagesschlüssel für den 09.12.2024 (UTC)
 
Tagesschlüssel 1:
Kasten: A    Kasten: B
0 4 6 A      6 9 E 3
F 1 3 E      7 2 4 D
7 C D 5      1 C 0 5
B 2 9 8      F 8 A B
 
And to simplify the encryption/decryption process, we could
do it this way. We only mirror from a -> b and b -> a, like:
 
With the seriation from above and the example box a and b:
 
Ciphertext: 90 B4 E1 etc.
 
This doublebox hex variation with only mirroring is IMHO
easy and would allow to transmit small binary blobs. :-)

I have now four programs ready. :-)

1. dkh (Doppelkasten Hex = doublebox hex)
2. dks (Doppelkasten Seration = doublebox seriation)
3. dkt (Doppelkasten Tagesschlüssel = doublebox daily keys)
4. dkk (Doppelkasten Krypto = doublebox crypto)

dkh takes an input file from stdin and pads it with 16 bytes
and produces always equal number of lines, due to padding, with
an output of 8 hex values per line. dks does then the seriation
and produces 16 hex bytes per line, with spaces between the values.

dkt produces n numbers of keys A and B per day, UTC time. With
a second version (for private use and not for sci.crpt) one can
generate the keys with a password and salt.

Finally dkk does the automatic  encryption from the dks file and
with a -d parameter the decryption, while using the produced key
files from dkt.

In the next couple of days I like then to run a Christmas Challenge,
with a given cipher message, to see how fast your rig can crack the
provided encrypted message. There are small prices for the Winner
and Runner-Up. I like to do this because I like to see how fast can
such messages been cracked, while I for myself do not do  cryptanalysis
and leave it to the experts like you.

--
Regards
Stefan