Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: colin <spamcollector393@gmail.com>
Newsgroups: sci.crypt
Subject: Re: HMAC cipher and a TRNG...
Date: Sun, 7 Jul 2024 09:58:54 +1200
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <v6cemu$3vkt2$1@dont-email.me>
References: <v69m0j$3e2id$1@dont-email.me> <v69vjv$3fu1v$1@dont-email.me>
 <v6cclq$3veiq$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 06 Jul 2024 23:58:55 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="13443f441876dc73da114b39731893b1";
	logging-data="4182946"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX192FzLmqa5w4sUEi4kMfo0HOQU6jlh0sxM="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:hU0CvbBeQVBEjA8hb3P2axJ/cys=
Content-Language: en-US
In-Reply-To: <v6cclq$3veiq$1@dont-email.me>
Bytes: 1903

On 7/07/24 09:24, Chris M. Thomasson wrote:
> On 7/5/2024 4:29 PM, colin wrote:
>>> Here is an example of my HMAC Cipher example. You should all be able 
>>> to examine the plaintext because it was encrypted using the default 
>>> key. Now, keep in mind, that if I encrypted this again, it would have 
>>> a different ciphertext. 
>> Security 101 - don't reuse passwords
> 
> :^) Indeed. However, creating radically different ciphertexts for the 
> same plaintext and password on a per-encryption bases is interesting to 
> me... Humm...

Your advertising campaign seems to to be pushing this fact as a selling 
point.

quote -
"Fwiw, it creates new ciphertexts for every encryption even with the 
same password and/or plaintext."

Where your encryption is only as strong as a compromised reused 
password. ( ie: pointless )