Skip to content Checksum drift can occur after setup due to unauthorized changes. Use the verification cron job:
maya secure verify runtime --user jdoe --manifest /etc/maya/manifests/user_manifest.sha256
Add to crontab for daily checks:
0 2 * * * /usr/bin/maya secure verify runtime --all-users --report /var/log/maya/daily_verify.log
The process is not a single step but a pipeline of verification checkpoints. Below is a step-by-step breakdown of Maya’s implementation. maya secure user setup checksum verification
A large bank uses Maya Secure for employee digital ID issuance. During user setup, the system verifies checksums of the corporate VPN configuration, certificate store, and time synchronization service. When a checksum fails due to a misconfigured proxy, the setup halts, preventing the employee from accidentally using a compromised network path. Checksum drift can occur after setup due to
Even after successful setup, the app stores a checksum of its final configuration. Every subsequent launch compares the live config against that stored checksum. If mismatched, the user is forced into a recovery flow. Add to crontab for daily checks: 0 2
Consumer side (during user setup):
Automated installers: