I dug up my old impl of scos2. Does this work for you?
scos2 247 742
*,B|A D@[>+i p"= ;_{ )3xy $yx5 ojts wihkb#
KWNYTZ JYFQV,H.Nw
rXZ
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.
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.
Here is the ciphertext for using Rich's original SCOS2 with a key of 3 7 ________
Hello World
________
Ko29_ 8/CDC
Can you decrypt it? Thanks.
I finally found the original SCOS2 code! Here it is:[...]
scos2 712 901
Chris M. Thomasson in sci.crypt:
[...]
I finally found the original SCOS2 code! Here it is:[...]
scos2 712 901
scos2 712 901
Marcel Logen in sci.crypt:
scos2 712 901
Sorry, this should read:
Marcel Logen in sci.crypt:
Marcel Logen in sci.crypt:
scos2 712 901
Sorry, this should read:
Please note the indentation.
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:The key is wrong, try:
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.
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? ;^)
"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:The key is wrong, try:
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.
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.
-28 -60
Yes, it can be read.
-71 -60
=~Bu :C ]}, [~ A~}#s
On 7/26/2024 8:36 AM, Marcel Logen wrote:[...]
Chris M. Thomasson in sci.crypt:
I finally found the original SCOS2 code! Here it is:
1930...9f
?
Chris M. Thomasson in sci.crypt:
1930...9f
?
That's OK.
But note: The indentation in the whole code is done by
two SPACEs per step. Exception: in the last "fprintf"
command.
On 7/30/2024 9:08 PM, Chris M. Thomasson wrote:
On 7/27/2024 12:20 AM, Richard Harnden wrote:[...]
On 27/07/2024 01:20, Ben Bacarisse wrote:
"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:
The key space is not that massive, so it can be brute forced for sure.
However, its interesting wrt the plaintext. What if the plaintext is
generated from a random source?
Afaict, if the plaintext is random, then its going to be hard to
identify it as a legit plaintext?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 498 |
Nodes: | 16 (2 / 14) |
Uptime: | 36:51:39 |
Calls: | 9,798 |
Files: | 13,751 |
Messages: | 6,189,334 |