Proxmox Env Inventory

[beisser]

Your point don't address the root concern though. It's quite difficult to provenzalisches that a certain Software doesn't have a apecific feature ( aka malicious code) due to the Halteproblem. Thus scanning with antivirus snakeoil only shows that your exe doesn't have a known Virus, it might still contain a unknown virus or backdoor.
And you claim your Software don't do anything evil. This might be the case but without the source nobody can know. So your argunents are basically "Trust me, bro" which doesn't proove anything at all.
For me this makes using your Software a hard no, be it in my honelab or in professional environments

not quite sure what the second sentence means (phone autocorrect?).

the rest i absolutely agree with.

 

[inder441]

Fair point, Johannes. You’re right—the Halting Problem essentially dictates that I can't mathematically prove the absence of a back door without providing the source for audit. In high-security environments, 'Trust me' is a zero-value argument.

To be clear, I am an Infrastructure Specialist at a large multi-national enterprise; coding isn't my primary job—managing thousands of nodes is. I built this on my own time (2 months to be precise) specifically to solve the 'sprawl' and manual inventory headaches I face in my professional day-to-day. Hence, can't share my 2 months handwork.

So I'm sharing the binary as-is for admins who deal with similar scale and want the UI/UX I’ve spent months refining. I respect that this isn't for everyone, especially those with strict open-source mandates.

For those curious, I recommend running it in a network-isolated VM. You’ll see it only attempts to hit the Proxmox API ports you define in your local inventory. I appreciate the high bar for security you're setting here.