Does GIMP plan to adopt a manifest-based plugin loading mechanism for Python-Fu to improve security?

Question

Goal: Determine whether GIMP will introduce a manifest‑based plugin loading mechanism for its Python‑Fu subsystem to strengthen script sandboxing.
Current behavior relies on the presence of executable script files in platform‑specific search paths, which offers limited protection against untrusted code placed in those directories. The uncertainty stems from the absence of an official roadmap and the need to maintain backward compatibility with existing Python‑Fu scripts across Windows, Linux, and macOS.
Does GIMP have a planned timeline for manifest‑based plugin loading? How would existing Python‑Fu scripts need to adapt to a manifest system? What security guarantees would a manifest provide compared to the current permission‑based approach?

Tasadduq Burney · Answer

Currently, there is no official roadmap or confirmed timeline for GIMP to adopt a manifest-based plugin loading mechanism specifically for Python-Fu. The architecture continues to rely on a discovery-based system where GIMP scans specific directories for executable scripts that register themselves.

The Current State of Plugin Loading
In current versions (including 2.10 and early-stage 3.0 builds), Python-Fu scripts are loaded by searching platform-specific paths (e.g., `~/.config/gimp/2.10/plugins/` on Linux). GIMP identifies valid plugins by their file extension and the internal registration code that calls the GIMP API. This approach offers minimal sandboxing; any script placed in these directories with appropriate execution permissions is executed by the GIMP process, operating with the same privileges as the user running the application.

Potential Impact of a Manifest System
If a manifest-based system were introduced, it would likely shift the security model from 'implicit execution' to 'explicit declaration.' This could theoretically provide:

Permission Scoping: A manifest could define which resources a script needs (e.g., network access, specific file system paths).
  Integrity Verification: GIMP could verify digital signatures within the manifest to ensure the script comes from a trusted source.
  Dependency Management: It could specify required Python libraries or versions, preventing the 'dependency hell' often seen in complex Python environments.

Challenges to Adoption and Compatibility
To adapt to such a system, existing Python-Fu scripts would likely require an accompanying sidecar metadata file (such as json or toml). This would break backward compatibility for thousands of legacy community-written scripts. The GIMP development team historically prioritizes accessibility, and a mandatory manifest system would serve as a significant barrier to entry for casual script authors.

Uncertainty and Verification
While the transition to GIMP 3.0 introduces a more modern plugin API via GObject Introspection, the focus remains on supporting Python 3 and improving stability rather than implementing a sandboxed manifest architecture. To determine if a specific feature is being discussed in development branches, one should monitor the GIMP GitLab for tags related to 'plugin-security' or 'metadata registration.'

Does GIMP plan to adopt a manifest-based plugin loading mechanism for Python-Fu to improve security?

1 answer

Currently, there is no official roadmap or confirmed timeline for GIMP to adopt a manifest-based plugin loading mechanism specifically for Python-Fu. The architecture continues to rely on a discovery-based system where GIMP scans specific directories for executable scripts that register themselves.

The Current State of Plugin Loading

Potential Impact of a Manifest System

Challenges to Adoption and Compatibility

Uncertainty and Verification

Your perspective belongs here.

0 question comments