Paru 2.2.1 introduces mandatory PKGBUILD reviews and Git security hardening
The Rust-based AUR helper now enforces re-reviews for updated repositories and mitigates terminal injection attacks.
Summary
Paru, the popular Rust-based AUR helper for Arch Linux, has released version 2.2.1, focusing heavily on tightening the security model for package reviews. The update introduces a stricter verification process where updates to previously accepted repositories must undergo a new review before application. This ensures that any changes to the PKGBUILD files are explicitly inspected by the user rather than being silently applied.
Beyond repository management, the release addresses several security vulnerabilities related to how the tool handles untrusted data. It implements protections against terminal control character injection in metadata and comments, and hardens the Git review process by ignoring external diff commands and repository attributes. These changes aim to prevent malicious actors from executing unintended commands or manipulating terminal output during the package review stage.
Security and Package Management Enhancements
- Repository Verification: Updates to accepted PKGBUILD repositories and URL-based repositories now trigger mandatory re-reviews unless the SkipReview option is active, preventing uninspected code changes.
- Git Hardening: To mitigate command injection risks, Paru now ignores external diff commands, text conversion, and repository attributes during change displays, requiring Git 2.40 or newer for compatibility.
- Input Sanitization: Terminal control characters in AUR comments, news, and package metadata are now escaped to prevent terminal manipulation, and signing-key values are protected from being interpreted as GPG command-line options.
- Dependency Logic: The tool now prompts for confirmation if a package lacks a repository prefix and a differently named repository package can satisfy the dependency, defaulting to the AUR if declined.
- Build Metadata: Paru has refined .SRCINFO generation to only target explicitly selected directories and has improved the handling of split packages and signing-key checks.
Why it matters
As a primary interface for the Arch User Repository, these changes significantly raise the security baseline for Arch Linux users by reducing the risk of supply chain attacks via malicious PKGBUILD updates. The requirement for Git 2.40+ and the stricter review workflows prioritize system integrity over convenience, which is critical for users relying on community-maintained software.
Original reference: linuxiac.com →