It's probably worth noting (on this oddly-stalled MIR...) that, despite ipmitool being in universe, it would be a complete lie to claim that Canonical doesn't already support it. We've patched it quite heavily here and there for both paying customer and community bugs, we use it quite heavily internally, and recommend it often externally. The part where it's managed to continue living in universe is really just a side-effect of none of its dependencies making it to main until now, not an explicit statement of support.

On the one hand, ipmi usually works on segregated networks because the implementation of ipmi on baseband controllers and NICs are usually pretty poor, so the risks may be limited. On the other hand, the compilation warnings are telling a story of a project that might have been Good Enough fifteen years ago, but looks unloved today.

Ideally we wouldn't promote this to main until someone cleans up the warnings. The compiler is giving hundreds of concrete suggestions to improve the code quality.

Security team NAK for promoting ipmitool to main. It's simply speaking too risky for our team to take on in a formal capacity. Feel free to consider re-opening if upstream drastically reduces the compiler warnings.