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: Memorizing a 128 bit / 256 bit hex key
Date: Tue, 18 Jun 2024 19:25:51 +0200
Organization: =?UTF-8?b?4oSt8J2UpfCdlKbwnZSj8J2Uo/CdlK/wnZSi8J2UrfCdlLLwnZSr8J2UqA==?=
 =?UTF-8?b?8J2UsA==?=
Message-ID: <v4sfv1$celq$1@i2pn2.org>
References: <v4s3ld$bu48$1@i2pn2.org>
	<v4s7nv$1cvio$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 18 Jun 2024 17:25:53 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="408250"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="uWi4uQdALkj7ETOfPbhNXfz0+Ra/gM5z6/Fa40dJi9U";
X-Spam-Checker-Version: SpamAssassin 4.0.0
Finger: tilde.club/~pollux/
Bytes: 1533
Lines: 18

Rich wrote:
 
> Given that the "dates" chunk the long string into "blocks", it might be 
> reasonable to use an erasure coding algorithm on the "blocks", and append 
> one or more blocks (i.e., dates) that are the erasure codes.  Then 
> forgetting (or misremembering) one or two of the dates might still 
> allow for recovery of the original key (or at least allow for detection 
> of a misremembering situation).

Well, I guess this would then need a program to handle, right?

My Idea is to use no program for that, so that no evidence can be
found on the device, in case someone is looking at it.

-- 
Regards
Stefan