Incorrect result for AES CTR 128 Bit about crypto HOT 7 CLOSED

On the latest git version this seems to work on eval, but fails on Node.js.

from crypto.

Yeah forgot to mention, I'm on nodejs

from crypto.

Maybe this is some bug in Haxe . I trace the bug to the current example :

        var key = haxe.io.Bytes.ofHex('b5cb4d8dd2c2fc705e10a825000043ff');
        key.set(15, key.get(15) + 1);
        trace(key.get(15));

This will show 256 in JS target and 0 for eval . The correct value should be 0.

I also test Java and Hashlink , both return 0 .

from crypto.

Open issue here : HaxeFoundation/haxe#9415

from crypto.

Thanks, but it is possible to put a fix (could be behind a define) here too?

from crypto.

Your fix would works, but I think the problem is from Haxe side. If someone want to merge it and follow progress on the Haxe side , I'm ok with that.

from crypto.