Problems with unsigned components of the PortableApps edition of GIMP on Windows 11

This is a reply to “Request for Code Signing of Unsigned GIMP Exectutables” which unfortunately has been closed already

Yesterday, the following problems on Windows 11 with Smart App Control on hit me: it blocks `gimp-3.exe` launching, then blocks every plug-in exe it spawns (`file-jpeg.exe`, etc.) with a “did not meet Enterprise signing level requirements” error. From a user’s perspective it just looks like “GIMPPortable can’t open a JPEG” - nothing points at signing being the cause.

I ended up switching to the MSIX Store build to keep working, but would rather stick with the portable version.

Also saw [GitLab issue #13715]( Auto signing .exe installer package (and binaries inside too) (#13715) · Issues · GNOME / GIMP · GitLab ) from which it looks like releases get signed by one maintainer with a personal cert, which doesn’t scale to signing every plug-in binary automatically.

Therefore it might be worth a look at [SignPath Foundation]( SignPath Software Integrity Platform - The free Code Signing & Software Integrity solution for Open Source Projects ) which is a free OV code signing for qualifying open-source projects, managed CI pipeline, built for exactly this “no in-house cloud-signing setup” case. [DB Browser for SQLite]( Signing Windows executables - Our journey with SignPath - DB Browser for SQLite ) did this migration and blogged about it, might be a good reference.

I’d be happy to test a signed build if that helps. Because this is only going to hit more people as Smart App Control becomes more common on Windows 11, I think.

Hi! If you mean PortableApps specifically (GIMP Portable | PortableApps.com), I’m afraid that the GIMP developers don’t manage that particular package. You’d need to contact them about signing.