
How to
Encrypt
a One Time Pad
Message using the
Simplest CT-46 Automated Method |
|
These instructions incorporate Dirk Rijmenants' splendid
automated OTP encrypt/decrypt utility based on the conversion
table CT-46. Download the
CT-46 Utility. Change the filename extension
from .jpg to .zip and follow the
instructions. |
|
1. Open a new text file in which
to save every step, then archive it when your
message has been fully decrypted. That will
make troubleshooting less tedious should it not work
correctly. |
|
2. Write your message text as concisely
as possible and save it to the text file.
Keep the text file open. |
|
3. Check the date of the message, is it
an odd or an even day? Read a
description of key pages
here. Download the key page text files for Odd
Days and
Even Days to make
it easy to copy and paste to the CT-46 utility. |
|
4. Decide on a key locator group from
anywhere in the key page, then copy it and at
least 50 % more key letters as there are letters in your
message text, to your text file.
If you have chosen a key locator close to the bottom of
the page, it will likely be necessary to copy all the
groups below it, plus more groups working down from the
top. Save all groups to your text file. |
|
5. With the encryption utility
open, past your in clear message text into the
upper field. |
|
6. Now, without including the key
locator group, paste all other key page groups into the
lower field. |
|
7, Click on Encrypt (-), the
in-clear message text will change into 5-digit groups.
This is your encrypted OTP message. Copy it to
your text file and save. |
|
8. Prepare a QTC preamble in the usual
manner and copy the encrypted message, now in 5-digit
groups into the message text field. |
|
9. End the QTC with an OPNOTE showing
where to find an appropriate decryption utility. |
|
|
|
|
|
|
Listeners are invited to join in by copying
encrypted traffic regardless
of the addressee, decrypt it and send the result by email to:

Guaranteed acknowledgement. If no reply within
48 hours please resend.
Before transmitting any
encrypted messages on the SAS Net,
please become familiar with the
Rules of Engagement
to ensure compliance.
Messages in clear are not covered by the Rules of Engagement.
Here's
an opportunity to put your CW skills to serious use through
innovation, challenges,
encryption and plain-text QTCs.
Between weekly nets, calling frequencies are
3.567 MHz and 7.1974
MHz,
for testing and encryption experimentation purpose.
Please
send your formal, encrypted QTCs
via the Thursday SAS Net ...
so that
everyone has the opportunity to participate.
A resource providing many encryption options,
not all are suitable for CW:
https://cryptii.com/
It runs on your browser Java platform and does
not need installation ... try it, it's clever, but
understand
you are undertaking an academic exercise without experiencing a
hands-on machine.
Experimentation with
diverse encryption methods is welcome, so long as a
URL pointing to an ad hoc decryption facility is made
available, either via
an OPNOTE giving a URL (recommended) or verbosely (not recommended).
|