Skip to content

Security: DaemonCores/DaemonCores-Phone

Security

SECURITY.md

Security policy

AstralEmu Banner

Simplify and Innovate for Everyone. Documentation Community Debian Bootc

Identify gaps and fill them, make improvements where possible, but above all, empower developers to offer more to users.


Private reporting

Use GitHub private vulnerability reporting or email guillou.gabriel@gmail.com. Do not open a public issue for an undisclosed vulnerability.

Supported state

The project has no released or supported phone image. Security fixes target the current source tree and its development tooling.

Sensitive areas

  • Future ADB probes must exclude personal data and unique device identifiers unless explicitly required and consented to.
  • Device descriptors must not contain credentials, proprietary blobs, or non-redistributable material.
  • Kernel, firmware, and boot-image inputs must be pinned and verified before use.
  • Flashing and partition operations must be opt-in, explicit, and paired with recovery instructions.
  • Build workflows must not expose registry, signing, or repository credentials to untrusted code.

Reports concerning probe privacy, malicious descriptor input, unsafe output paths, dependency execution, artifact substitution, or destructive device operations are in scope.


Made with ⭐ by the DaemonCores community Documentation Community Debian Bootc

There aren't any published security advisories