Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: sci.crypt
Subject: Re: Seriation
Date: Sun, 8 Dec 2024 16:05:56 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <vj4g54$3sqat$1@dont-email.me>
References: <vj1pgp$5u55$1@paganini.bofh.team> <vj2fc0$3bbjk$1@dont-email.me> <vj2os2$ch7p$1@paganini.bofh.team> <vj3cil$3keo5$1@dont-email.me> <vj412r$ehh2$1@paganini.bofh.team>
Injection-Date: Sun, 08 Dec 2024 17:05:58 +0100 (CET)
Injection-Info: dont-email.me; posting-host="5bbb81f215d7d1f8b55fb1ec57d67ed5";
	logging-data="4090205"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19NYI2EzBeqglHGnUqA3gcD"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:NZPIjMtKi5yYsCc4h0n+20H+zOw=
Bytes: 1488

Stefan Claas <pollux@tilde.club> wrote:
> Rich wrote:
> 
>> And why would you think it would not also eventually be "cracked" and 
>> "floating around on bitmessage" after some time?
> 
> I do not think that, I only propose something else to use.

Ok, fair enough.  But does it add anything of value over SCOS?  SCOS's 
'value' was in the practice of analysis and working out the algorithm 
given just the encrypted messages (plus an 'oracle' who would encrypt 
requested messages).

The actual 'obsfucation' factor was secondary.