Re: HMAC cipher and a TRNG...

On 7/7/2024 12:33 PM, Chris M. Thomasson wrote:

On 7/6/2024 2:58 PM, colin wrote:

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.

 Selling point, what do you mean? This is an experiment! It would be fun if somebody could bust it wide open. Where they don't need a damn password, the ciphertext is all they need. That would be fun to learn about. Advertising campaign as in I need it to be properly examined before it can be used at all. Forever experimental it shall be.
 :^)
 

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 )

If somebody has your secret key for any symmetric cipher, well, that is bad, right? I must be missing something.

 A compromised secret password is bad. I was just interested if I could create different ciphertexts for the same plaintext and password, as an experiment. See?