Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: Stefan Claas <fgrsna.pynnf@vagrearg.eh>
Newsgroups: sci.crypt
Subject: Re: The lost key
Date: Mon, 31 Mar 2025 14:42:31 +0200
Organization: i2pn2 (i2pn.org)
Message-ID: <450056e3ef85921f1b01693bb8baaec0301e0e78@i2pn2.org>
References: <vs48nd$ut3s$1@dont-email.me> <vs9f2j$20s45$1@dont-email.me> <vs9hme$23q5k$1@dont-email.me> <vs9lu9$2733f$1@dont-email.me> <vsah6h$358a2$1@dont-email.me> <vsakth$3anr9$2@dont-email.me> <vsbqdf$1qfti$3@dont-email.me> <vsc2lj$23qv2$1@dont-email.me> <vsc6k8$27l0j$2@dont-email.me> <vsc779$28n4g$1@dont-email.me> <vsc7kv$28n4g$3@dont-email.me> <911abeff935ff9ebbc7e13ee9505f7dcaddf8202@i2pn2.org> <vsc92d$2aepg$4@dont-email.me> <2f4b2876f94bb26d48d3fd8069118a261a0d06d3@i2pn2.org> <vsch3g$2ie74$1@dont-email.me>
MIME-Version: 1.0
Injection-Date: Mon, 31 Mar 2025 12:42:31 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="2534850"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="ieSrCjSDShpZNyqIW52mlwIkg76Hsp+TOOO6KTdfCN8";
User-Agent: flnews/1.3.0pre29 (for GNU/Linux)
Cancel-Lock: sha1:vU2nYSxWRyCwaERZj7aPNcEfLd4=
X-Date: It's Mon Sep 11535 02:42:31 PM CEST 1993, the September that never ends.
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Ed25519-Sig: ad73d4862ecd3bff35cfe3e3895549a6c567ccfc6f44635fd451e3b7bf18cb9f
 c930f7dc3e56162a1a6da713cc97b462adb940fe64431ee531a2906a048a900a
X-Ed25519-Pub: c0ffee5a36e581eb10f60b2831b3cdb955d2e7ef680dd282a8d43ad8b84b357a
Bytes: 2789
Lines: 32

Rich wrote:
> Stefan Claas <fgrsna.pynnf@vagrearg.eh> wrote:
> > I do not have any client problems at all, because as a Usenet reader I
> > use flnews, which is stricly RFC conform.
> 
> Ok, so your client works properly.
> 
> > The problem occurs when trying to decode small SCOS messages in bash 
> > via echo.
> 
> Now I have to ask, why would you use echo in bash to decode?
> 
> If your scos decoder reads from standard input (which it must if you 
> use echo to feed it a SCOS message), then just run it in a terminal, it 
> will wait for input from standard input (which is now the terminal, and 
> no 'character changes' will occur, that is unless you've reconfigured 
> your terminal quite a lot from its standard settings).
> 
> Then paste in the SCOS message into the waiting standard input in the 
> terminal, and hit ctrl+d (end of file) to signal the end of file.
> 
> Your scos decoder will then receive your pasted data, unaltered, do the 
> decode, and print its output.
> 

Good suggestion, thanks!

Regards
Stefan

-- 
Onion Courier Home Server Mon-Fri 15:00-21:00 UTC Sat-Sun 11:00-21:00 UTC
ohpmsq5ypuw5nagt2jidfyq72jvgw3fdvq37txhnm5rfbhwuosftzuyd.onion:8080 inbox