Several win32 executables are not signed

[dozer75]

Actual Behavior

The following executables is not signed, this causes AppLocker issues in organisations that requires signed executables.

AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\docker-buildx.exe
AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\docker-compose.exe
AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\docker-credential-ecr-login.exe
AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\docker-credential-wincred.exe
AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\helm.exe
AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\kubectl.exe
AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\kuberlr.exe

Others are signed, so it is a bit inconsistent in the installation and it would be nice to have them all signed.

Steps to Reproduce

• Install 1.13.1 of Rancher Desktop.
• Go to the installation folder and execute ls -Recurse *.exe | Get-AuthenticodeSignature to see files that isn't signed.

Result

The listed applications are prohibited to be executed in a Windows environment protected by AppLocker.

Expected Behavior

All executables should be signed.

Additional Information

I found #5003 as a open issue, but that one is signed now.. Currently it is those I have specified that isn't signed.

Rancher Desktop Version

1.13.1

Rancher Desktop K8s Version

1.29.4

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Enterprise N 23H2 22631.3447

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

[mook-as]

Hmm, those executables are not currently signed because we're not currently building them from source. We should probably do so…

[dozer75]

It would be nice to have them signed for better enterprise handling...