Security
Security is ordinary engineering.
Use trusted packages, keep systems current, keep services deliberate and report a genuine flaw privately. Saphira and SaphiraD give you the same package trust model; you choose the init system, we keep the operational path clear.

The short version
Keep the system updated. Keep services intentional. Tell the right maintainer privately when something is wrong.
Most security corrections on Saphira are ordinary package upgrades. That is not complacency; it is how a maintained operating system is meant to work. Review important changes, take backups appropriate to the workload and update without waiting for a headline.
apk update
apk upgradeThe first command refreshes the signed repository metadata. The second installs the available package upgrades. A corrected library or runtime is not necessarily loaded by a program already running, so restart or reload the affected service when its own documentation says to do so. Containers, custom builds and software installed outside APK need their own update process.
How Saphira keeps the chain of trust visible
Saphira packages are obtained through the native APK repository. Repository indexes and published APKs are signed; the package manager checks that trust information as part of normal package work. Downloads are also published with SHA-256 checksums so an operator can verify the file they received rather than relying on appearance or a browser lock icon alone.
- • The package repository is served over TLS and its indexes are signed.
- • Every published image has a SHA-256 checksum you can verify yourself.
- • Sources are pinned and hash-verified before they enter a build.
- • The installed service set is minimal: nothing runs merely because it exists.
- • Published image downloads will use short-lived authorization before the archive is served directly.
Saphira and SaphiraD package OpenRC and systemd service definitions together, but do not silently enable a service just because its software was installed. Review what is listening, what starts at boot and which account each service runs as. Small, explicit service sets are easier to understand and maintain.
Verify a download
Download the checksum file from the same official release location as the archive, then run the command from the directory containing both files:
sha256sum -c saphira.tar.xz.sha256A successful result confirms the archive matches the published checksum. A mismatch is a reason to stop, delete the local copy and obtain it again from the official source; it is not something to work around.
If something looks wrong
Start calmly. Record the package version, service status, relevant logs and the time the behaviour was observed. Preserve enough evidence to understand the problem, but do not turn a suspicion into broad destructive testing or a public incident report.
If there is immediate operational risk, take proportionate local action: limit public exposure, use a known-good backup or fail over where that has already been designed. A service running PHP, OpenSSH, Docker or another widely used component is not, by itself, evidence that it has been compromised. Check the installed version and the relevant advisory before deciding what is needed.
Saphira tracks upstream security work, packages applicable corrections and publishes Saphira-specific defects separately. See Bugs and upstream security advisories for the public record. SVE identifiers are reserved for defects originating in Saphira-developed software, not every upstream CVE carried by a package.
Reporting a vulnerability
Do not submit exploitable security vulnerabilities through the public bug tracker or the contact form. Use the dedicated security contact so a fix can be prepared before details are public.
Security contact
security@akadata.ltd
Include the affected release, the component, and enough detail to reproduce. Include the impact you observed, concise reproduction steps, package versions and logs with passwords, tokens, personal data and unrelated system details removed. Stop once there is enough evidence: do not collect data, establish persistence, degrade a service or keep probing merely to make a stronger demonstration.
First decide who owns the fault. A vulnerability in unmodified upstream software should normally be reported to that upstream project first. Report directly to AKADATA when it concerns Saphira code, Saphira packaging, a Saphira-specific patch or integration, Saphira infrastructure, or an AKADATA-operated public service.
The full scope, safe-research rules and disclosure process are in the Responsible Disclosure policy. There is no bug bounty and no response-time promise unless separately agreed.
Machine-readable security contact
Security tools and researchers can discover the same reporting route through /.well-known/security.txt. It identifies the private contact and the canonical policy page.
This file is a signpost, not permission for active testing. The Responsible Disclosure policy remains the authoritative statement of scope and conduct.