e4m2

Looks like a mistake in the article, it should probably say:

    I compare these bytes with the quotes and backslash characters.

Which would correspond to the two _mm512_cmpeq_epi8_mask calls in the source code.

Those who have to comply with their standards (e.g. FIPS 140-3), at the very least.

The author maintains an AWK implementation:

https://github.com/benhoyt/goawk

Also FNA (https://fna-xna.github.io), which is aimed at 100% compatibility with existing XNA 4.0 code.

But is there an actual alternative?

PeaZip directly uses 7-Zip under the hood.

NanaZip is a fork of 7-Zip. While it's certainly a very good effort, it's focused on modernization and AFAIK doesn't fix many of the issues brought up in the article.

WinRAR is the "obvious" competitor, but it's completely non-free and also Russian-made (though the company itself is German).

Author's presentation on the topic: https://github.com/TheOfficialFloW/Presentations/blob/master... (video not yet available)

Public reimplementation: https://github.com/sleirsgoevy/bd-jb (not a "full" jailbreak yet, the kernel part is missing)

To clarify, this exploit only works up to firmware 9.04 on the PS4 and up to 4.51 on the PS5.

Download the build tools[0] and choose the appropriate options. I'd personally consider the following a good baseline: MSVC v143, CMake tools, Windows 11 SDK, Clang tools (if you don't want/need these you can shave off 3.5 GB). `zig cc` is another interesting alternative, it's just a single ~62 MB download.

[0] https://visualstudio.microsoft.com/downloads/#build-tools-fo...

> Are derived community works, like say the D-language, Dart, or Zig bindings to the win32 API which are generated from those files open source - if Microsoft did not release them as such?

Certainly. The source for these bindings is the WinMD file, which is MIT licensed. While it is true that its contents are generated wholly from non-FOSS sources, it doesn't impact end users of the metadata. Microsoft owns the original IDL/headers and can choose to license any related work however they like.

Vale compares its safety to Rust's on a few occasions[0][1] and the exact opposite claim is made, i.e. Vale is safer than Rust.

[0] https://verdagon.dev/blog/hybrid-generational-memory#afterwo...

[1] https://vale.dev/comparisons#safe

Unfortunately, the naive way also turns out to be wrong in C. uint8_t gets promoted to a signed int when shifting, which in turn causes undefined behavior for specific input. One way of fixing this is casting to the desired type before the shift, thus avoiding surprising conversions.

On a side note, compiler warnings and sanitizers help with this kind of stuff greatly, use them if you have the option: https://godbolt.org/z/8oq9GTcze