Replace handle.exe with fshc.exe

[lukebakken]

handle.exe does not reliably produce parsable output. On top of that, it is closed source abandonware.

We should replace it with a small open source alternative our team members have developed as a personal project.

Some things involved

• Figuring out how best to release fshc.exe.
• Ensuring that the necessary Windows runtime components are available (they probably are).
• Integrating the executable into the Windows zip and installer.
• Signing the fshc.exe executable.

Migration Strategies

fhsc can continue being an optional dependency that, unlike handle.exe is open source and can produce easier to parse output (JSON).

1. handle.exe will then be deprecated
2. Both will be supported for a period of time
3. fshc will eventually become the only option

Or, for 4.1.0 or 4.2.0, we can stop supporting handle.exe since it is optional already, and
move straight to using fshc's JSON output.

Right now the biggest item left is a an Actions workflow that would produce 64-bit builds of fshc for Windows, Linux and macOS (the latter two for anyone who may need it, not for RabbitMQ's own needs).

References

• Windows: handle.exe output did not contain a line beginning with 'File', so parsing of its output fails #12360
• https://github.com/rabbitmq/rabbitmq-server/issues?q=is%3Aissue+handle.exe

[michaelklishin]

fhsc can continue being an optional dependency that, unlike handle.exe is open source and can produce easier to parse output (JSON).

1. handle.exe will then be deprecated
2. Both will be supported for a period of time
3. fshc will eventually become the only option

Or, for 4.1.0, we can stop supporting handle.exe since it is optional already, and
move straight to using fshc's JSON output.

Right now the biggest item left is a an Actions workflow that would produce 64-bit builds of fshc for Windows, Linux and macOS (the latter two for anyone who may need it, not for RabbitMQ's own needs).

[Digiover]

For what it's worth, handle.exe (or Windows in general) requires administrator privileges to list file and socket handles and information, as described in the "Installation" section of the documentation.

Notice the difference:

In both sessions I started C:\Windows\System32\handle64.exe -nobanner | more.

I'm unsure why the notice is logged when RabbitMq runs as Local System and starts / spawns handle.exe. Maybe someone can catch that using ProcMon :)

[michaelklishin]

IMO as of 1.2.0, fshc is ready to be integrated.