• =?UTF-8?Q?Re=3A_Browser=E2=80=91only_HMAC=E2=80=91based_toy_cipher_?= =?UTF-8?Q?demo_=28DrMoron=29_=E2=80=94_now_live_with_URL=E2=80=91encoded_ci?= =?UTF-8?Q?phertext?=

    From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to sci.crypt on Mon Feb 23 12:54:51 2026
    From Newsgroup: sci.crypt

    On 2/22/2026 2:34 PM, Ben Bacarisse wrote:
    Rich <rich@example.invalid> writes:

    Ben Bacarisse <ben@bsb.me.uk> wrote:
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:

    On 2/20/2026 2:03 PM, Ben Bacarisse wrote:
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:

    On 2/20/2026 1:01 PM, Ben Bacarisse wrote:
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:

    On 2/20/2026 5:07 AM, Ben Bacarisse wrote:
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes: >>>>>>>>>
    Password with unicode = can of oh shit's!, not just a can of worms? >>>>>>>>> They introduce some difficulties, but there are advantages as well. >>>>>>>>> People want to use passwords and pass phrases that are in their native
    language. It can help people choose longer ones while still remembering
    them. Also Unicode can increase the entropy without needing longer >>>>>>>>> passwords. Using raAEYc+-+rCR-i-+-# as a password is probably quite strong, though
    many places will either reject it or insist I add a digit, an upper and
    lower case letter and a symbol!


    Well let me try with just copy-and-paste between the quotes
    "raAEYc+-+rCR-i-+-#" as a
    password for the plaintext, between the quotes:

    "Ben Bacarisse"

    Here is the link to some ciphertext... Can you decrypt it? copy paste in
    the password, click the decrypt button:

    https://fractallife247.com/test/hmac_cipher/drmoron/?ct_hmac_cipher=ce71abab3bb661afc83142e0d7a59abfb80348bffcbe8c3659c00cf015d04d06f4d4f9795e6d5f40db058651609680a0e98a00b236ebf962fb264f5642bdf431402b322dd186a92655a6e9d551c0d4d3068fb7f4d1d7
    I don't want to copy an post stuff into a link. What purpose does that >>>>>>> serve? You know what your code does so you know what will happen for a >>>>>>> particular sequence of input bytes.

    I still think it scary because of what I read in this thread. Might work,
    might not??? Perhaps? Humm... ;^o
    The trick to knowing if some software will do what you expect is to >>>>>>> understand the code, the inputs and the outputs. Copying and pasting >>>>>>> text won't teach you much about any of these things.

    Well, if you are on a different system and the copy and paste might give >>>>>> different bytes for the same visual symbols, that would murder the password
    and you could not decrypt... Right?
    Yes it would. But so what? If your code handles the input correctly, >>>>> why do you care if I can paste something into a website correctly?

    I wanted to see if you can post those visual symbols as a password and make
    it not decrypt the plaintext correctly. It would give an example of the >>>> potential problem we are discussing here? Ala, Rich and Marcel 's point? My
    hash would not work if its not bit exact...

    I don't think any of the symbols I posted can illustrate Rich's point
    and even if I had chosen ones that did, I would be surprised if copying
    and pasting would trigger normalisation. But let's say it's a
    concern... Then a good way to illustrate that point would be a website
    that just showed what bytes are pasted into an input field. Having hash >>> code behind it just obscures the problem. The problem would not lie in
    the hash but with the system that's doing the copy and paste (and the
    details of how the HTML form in handled server side).

    Richard Harnden, in Message-ID: <10n52nf$2t5lv$1@dont-email.me>, took
    care of that part for me:

    For UTF-8, "|i", for example, could be any of:

    The precomposed character: c3a1 - 11000011 10100001,
    "a" plus a combining-acute: 61cc81 - 01100001 11001100 10000001,
    or some overlong encoding that takes up more bytes than it actually
    needs.

    I'm not sure why you are reposting this. My point to Chris was that his website was not a good way to test if copy and past is working as he
    expects since it does show the input bytes and just adds an extra level
    of complexity to the test.

    Now, proper confirming implementations should not issue "overlong"
    encodings, so with the exception of pen-testers, Chris *should* be able
    to ignore the "overlong" angle.

    There are cases where overlong encodings can cause problems and there is nothing to stop these being generated maliciously so the usual advice is
    that programs should check for these on input.

    But Richard's post shows two different byte strings that produce the
    identical visual character.

    Yes. I didn't think this was in any doubt.


    Right. I need to allow a user to see the raw hex bytes from password and
    the plaintext.
    --- Synchronet 3.21b-Linux NewsLink 1.2