Deutsch   English   Français   Italiano  
<36ff659705199d63deed8b0e58ecfc38344ac07d@i2pn2.org>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: Stefan Claas <pollux@tilde.club>
Newsgroups: sci.crypt
Subject: Re: Inspired by Chris's HMAC cipher
Date: Fri, 18 Oct 2024 15:53:57 -0000
Organization: Ch1ffr3punk5
Message-ID: <36ff659705199d63deed8b0e58ecfc38344ac07d@i2pn2.org>
References: <d362d3df17bfa32425c931d333a3a53be0c31bd0@i2pn2.org> <ve1fqq$1r205$1@dont-email.me> <e21b4f8f4c4c60ee76caf01ad8b5a13a329ad51b@i2pn2.org> <3fdb83dbfe35a57d62d07ea352ccc53a9b6e01cf@i2pn2.org> <4742d35c14f5b945a681c331e6661d57e8bb8b96@i2pn2.org> <verr74$2stfq$2@dont-email.me> <7e059f0438e1e4be5778f2d7f83b8a94202a2149@i2pn2.org> <vesa0l$2v6q6$2@dont-email.me> <2894de1054fe9a8e4af84661b76d8b7d0cbd0e7b@i2pn2.org> <vetopp$3b04k$1@dont-email.me>
MIME-Version: 1.0
Injection-Date: Fri, 18 Oct 2024 15:53:57 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="2608320"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="ieSrCjSDShpZNyqIW52mlwIkg76Hsp+TOOO6KTdfCN8";
User-Agent: flnews/1.3.0pre12 (for GNU/Linux)
Cancel-Lock: sha256:tIUmMyEMru2LjU/6YZxYaujDkcAf29vxx1p7AiL/gaU=
X-Ed25519-Pub: c0ffee5a36e581eb10f60b2831b3cdb955d2e7ef680dd282a8d43ad8b84b357a
X-Ed25519-Sig: f8a6255e60994eb7e44b379a93c7a0db1953a6271fd8746995365e0c8c79aa7b
 906423d86d082da8875250ea63f2d4c3ac493a605d8b065874d7cff4c8baa207
X-Date: It's Fri 11371 Sep 1993 05:53:57 PM CEST, the September that never ends
X-Spam-Checker-Version: SpamAssassin 4.0.0
Bytes: 2315
Lines: 21

Rich wrote:
> Stefan Claas <pollux@tilde.club> wrote:
> > I am also thinking of creating a key pair for sci.crypt, so that we 
> > no longer have to use SCOS, because SCOS was floating around on 
> > Bitmessage, as C, Pascal and Go code.
> 
> Do note that SCOS was not intended to be "secure" (for most definitions 
> of that word).  Richard H. posted it as an exercise in breaking a 
> cipher given just examples of the cipher's output.  It fits in as a 
> somewhat more difficult ROT13 than as a true "protection" for anything 
> posted with it.

Ok, understand.

> It is interesting that source for it is on bitmessage.

It has been a while since it was posted. New users may not be able
to fetch it, because Bitmessage has a TTL parameter.

-- 
Regards
Stefan