Security Policy
Relevant source files
The following files were used as context for generating this wiki page:
Quickemu is a Bash-based wrapper for QEMU designed to automate the creation and operation of optimized virtual machines for Linux, macOS, Windows, and BSDs. The security policy defines the supported versions for security updates and the procedures for reporting vulnerabilities, while the project's broader security posture is supported by rigorous development standards and community conduct guidelines.
Sources: README.md:12-19, AGENTS.md:3-5
Supported Versions
Quickemu maintains security support for the current major release cycle. Older versions are generally not supported once a new minor or major baseline is established.
| Version | Supported |
|---|---|
| 4.9.x | ✅ |
| < 4.8 | ❌ |
Sources: SECURITY.md:5-11
Reporting Vulnerabilities
As a community-driven hobby project, Quickemu handles security reports on a best-efforts basis without formal Service Level Agreements (SLAs).
Disclosure Process
Users who discover a vulnerability are instructed to use the GitHub issue tracker specifically via the "Report a vulnerability" option.
The diagram above illustrates the intended flow for security disclosures as outlined in the project documentation.
Sources: SECURITY.md:15-20
Secure Development and Maintenance
Quickemu employs several technical strategies to ensure the integrity and reliability of its codebase.
Integrity Verification
The project includes specialized utilities to ensure that downloaded assets (such as ISO images) are valid and have not been tampered with or corrupted during transit.
- chunkcheck: A dedicated utility for download verification.
- quickget: Incorporates logic for OS definition and secure download handling.
Development Standards
To prevent common script-based vulnerabilities, the project enforces strict coding standards:
- ShellCheck: All scripts (
quickemu,quickget,quickreport,chunkcheck) must be compliant with ShellCheck to avoid logic errors and shell-specific security pitfalls. - CI Validation: Automated workflows run ShellCheck (severity: warning) and validate Nix flakes on every Pull Request.
Sources: AGENTS.md:7-14, AGENTS.md:74-85
Community Security and Conduct
The security of the project environment is further protected by a Code of Conduct that governs interactions within community spaces, such as Discord and GitHub.
Enforcement and Privacy
Community leaders are responsible for enforcing standards of behavior to prevent harassment and the publication of private information (doxing).
- Confidentiality: Leaders are obligated to respect the privacy and security of any individual reporting an incident.
- Reporting Channel: Abusive or harassing behavior is reported via a dedicated channel on Discord.
Interaction Restrictions
Violations of community standards can result in progressive restrictions to prevent further impact:
| Severity | Action | Impact |
|---|---|---|
| Correction | Warning | Private warning and clarification of behavior. |
| Warning | Interaction Ban | Temporary restriction from interacting with specific community members. |
| Temporary Ban | Full Suspension | Removal from community interaction for a specified period. |
| Permanent Ban | Permanent Removal | Pattern of violation leads to total exclusion from community spaces. |
Sources: CODE_OF_CONDUCT.md:34-45, CODE_OF_CONDUCT.md:58-62, CODE_OF_CONDUCT.md:70-101
Summary
The Quickemu security policy relies on a combination of version-tracked updates, a standardized vulnerability reporting path through GitHub, and automated linting to maintain script integrity. While the project operates on a best-efforts basis without formal SLAs, the integration of verification tools like chunkcheck and strict CI workflows ensures a baseline of security for users and contributors.
Sources: SECURITY.md:18-20, AGENTS.md:74-80, README.md:13-19