Sujet : Re: an scos2 test...
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : sci.cryptDate : 31. Jul 2024, 19:33:54
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v8e02j$1n8am$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Mozilla Thunderbird
On 7/31/2024 3:24 AM, Richard Harnden wrote:
On 31/07/2024 05:09, Chris M. Thomasson wrote:
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?
If the plain text is random, then you'd never know if you got the correct decrypt anyway.
Bob would know the correct decrypt because he has the same secret key as Alice? So, for some reason Alice wants to send some random data to Bob, but encrypts it using SCOS2... Bob knows how to decrypt it via the secret key... Eve might not be able to get at the data even with brute force? Is this fair enough or moronic? ;^o
It only works for English (or C) text. It seems to work okay for French and "lorem ipsum". It doesn't like German.
It's doubtless slower cpu-timewise that brute forcing. It saves on eyeball-time.