Chris M. Thomasson wrote:
On 10/20/2023 4:16 PM, Stefan Claas wrote:
Z ,Go1 ,Id
Is that a header?
It is part of a SCOSv2 message.
To decode the message you have to look at the
Message-IDs first part, which is crockford base32
encoded. Hence the Subject: name.
On 10/20/2023 4:16 PM, Stefan Claas wrote:
Z ,Go1 ,Id &{M,2Afu= 'Yu)Jat~Q Q u'|T! ,Ca4=Oc/ my-
b~Zy -;Qi{/f
d~,Vo[
Base64?
On 10/20/2023 4:16 PM, Stefan Claas wrote:
Z ,Go1 ,Id
Is that a header?
Stefan Claas <stefan.claas@iris.to> writes:
Chris M. Thomasson wrote:
On 10/20/2023 4:16 PM, Stefan Claas wrote:
Z ,Go1 ,Id
Is that a header?
It is part of a SCOSv2 message.
To decode the message you have to look at the
Message-IDs first part, which is crockford base32
encoded. Hence the Subject: name.
Or one can just search the key space, which is small. That works well
enough because most SCOS texts are recognisable language.
So I wish you the same, Stefan.
On 28/10/2023 10:52, Stefan Claas wrote:
Ben Bacarisse wrote:
Or one can just search the key space, which is small. That works
well enough because most SCOS texts are recognisable language.
Thanks, but how does this work in general? I mean if someone writes
a SCOS message cracker, will it print to stdout all decoded tries
and then uses, grep like, some key words, so that the user can see
the plain text in one of the decoded messages, which he has to go
through?
Because scos leave spaces alone, I just look for 3-letter words with
a consistent increament and print out the best hits. It seems to
make a fairly good guess ...
eg:
| $ cat x
| Z ,Go1 ,Id &{M,2Afu= 'Yu)Jat~Q Q u'|T! ,Ca4=Oc/ my-
|
| b~Zy -;Qi{/f
| d~,Vo[
|
| $ ./decode_scos x | ./scos
| ./decode_scos: Not sure, but ...
| > -17 -14
| > I 62=+ CAH fZpL3~EFT Miq0)+]GV H Xspv} ,'\OSll~ TRZ
| >
| > 7Fdo wt59>:Q
| > Algrw_
|
| > -17 -24
| > I wish the sci.crypt community a great weekend! :-)
| >
| > Best regards
| > Stefan
|
| > -67 -14
| > z IEYX try =*:2Fevw! 3[/CUXcx$ y ^.:<a nfp59~~e !8*
| >
| > Jw-; \>HLmi7
| > r~{?\V
|
| > -67 -24
| > z \[.} >}+ ._[l_?A:> _;'',@[>A ( {?+(> \++#+@-M iWU
| >
| > s+.> ?+{(?-.
| > 9>+=(@
Otherwise, there are only about 8000 possible keys - so brute forcing
is easy.
Also: The Message-ID should be set be the server, not you.
Duplicates would cause confusion. Hide things in an X-something
header.
Chris M. Thomasson wrote:
On 10/20/2023 4:16 PM, Stefan Claas wrote:
Z ,Go1 ,Id
Is that a header?
It is part of a SCOSv2 message.
To decode the message you have to look at the
Message-IDs first part, which is crockford base32
encoded. Hence the Subject: name.
Chris M. Thomasson wrote:
On 10/20/2023 4:16 PM, Stefan Claas wrote:
Z ,Go1 ,Id &{M,2Afu= 'Yu)Jat~Q Q u'|T! ,Ca4=Oc/ my-
b~Zy -;Qi{/f
d~,Vo[
Base64?
No, it is SCOSv2
Sorry about that. Btw:fceb3d1d17deb327eaa475df2a6c3aed13467375adcd5c0c2f4fcb56a39070cd3c2afa54936ac8da5459ab83a8e2c6e57a64b495e0ea515275023488ab0e0bc69dbcf0717c367ced7c093bf76d89288ad8fe4a20f793fc6b306f0c5d11ac755f726969ca0385a1dcc8b0c2eaad6e384c173cb41dec89f847c96cb2e651882e9
http://fractallife247.com/test/hmac_cipher/ver_0_0_0_1?ct_hmac_cipher=
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 487 |
Nodes: | 16 (2 / 14) |
Uptime: | 00:57:17 |
Calls: | 9,660 |
Calls today: | 2 |
Files: | 13,709 |
Messages: | 6,166,517 |