Sujet : Re: an scos2 test...
De : ben (at) *nospam* bsb.me.uk (Ben Bacarisse)
Groupes : sci.cryptDate : 27. Jul 2024, 01:20:34
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <87bk2j65yl.fsf@bsb.me.uk>
References : 1 2 3 4 5
User-Agent : Gnus/5.13 (Gnus v5.13)
"Chris M. Thomasson" <
chris.m.thomasson.1@gmail.com> writes:
On 7/26/2024 2:32 AM, Richard Harnden wrote:
On 26/07/2024 06:15, Chris M. Thomasson wrote:
On 7/25/2024 8:54 PM, Rich wrote:
scos2 65 33
>
0ZGS XB sJ@ lH ~i<8/
>
For some reason I am getting a plaintext of:
>
~U9o My 8/g v[ Ym9\;
>
using my impl and Rich's original scos2 impl.
The key is wrong, try:
28 60
0ZGS XB sJ@ lH ~i<8/
>
Indeed it works like a charm. It had to be a "key issue". Humm... That
would be a fun test? Try different keys and log "readable" results wrt
decrypted plaintext? ;^)
Yes. Somewhere I have a program that just tries all keys. I was going
to get it to stop when English (or C) letter frequencies were found but
it turned out simpler just to eyeball the output. As a human, you can
spot a decrypt a mile off and, if I remember correctly, SCOS has "close
decrypts" that I could spot but which would look, statistically, like
plaintext.
-- Ben.