Integrity Check
🛡️ File Information
| Property | Value |
|---|---|
| Binary Name | integrity-check |
| Version | 9.0.1 |
| File Size | 9.4MB |
| Author | Warith Al Maawali |
| License | Proprietary |
| Category | Security & Authentication |
| Description | A system integrity checker for verifying script and configuration files |
| JSON Data | View Raw JSON |
SHA256 Checksum
🛡️ Key Features
Integrity Verification
| Feature | Description |
|---|---|
| Hash Verification | SHA256 checksums for all tracked files |
| Signature Validation | Cryptographic signatures prevent forgery |
| Version Tracking | Compares local vs remote package versions |
| Configuration Auditing | Validates config file syntax and security |
Why Integrity Check is Essential
| Benefit | Description |
|---|---|
| Tamper Detection | Immediately identifies modified system files |
| Malware Prevention | Detects unauthorized changes to binaries |
| Security Auditing | Regular verification ensures system integrity |
| Compliance | Maintains audit trail of system modifications |
🛡️ ⚡ TL;DR - Essential Commands
# Verify integrity of all tracked files
sudo integrity-check check_integrity
# Generate new baseline hashes
sudo integrity-check generate
# Verify cryptographic signatures
integrity-check check_signatures
# Run comprehensive check (integrity + versions + signatures)
integrity-check check_all
# View recent integrity logs
integrity-check view_logs
🛡️ Understanding System Integrity
How Integrity Checking Works
Integrity Check maintains a database of known-good file hashes and compares them against current files:
What Gets Checked:
| Location | Description |
|---|---|
| System Binaries | /usr/bin, /usr/sbin |
| Dashboard Scripts | dashboard/hooks/ |
| Configuration Files | /etc/ |
| Kodachi Binaries | Kodachi-specific binaries and tools |
Generating Baselines
After fresh installation or verified updates:
This creates a baseline of all file hashes that future checks compare against.
Signature Verification
Verify cryptographic signatures on signed files:
Signatures ensure files haven't been modified since signing by Kodachi developers.
Version Checking
Compare local package versions with remote repositories:
Identifies outdated packages that may have security vulnerabilities.
Configuration Validation
Verify configuration file integrity and syntax:
Ensures configuration files haven't been corrupted or maliciously modified.
Comprehensive Security Audit
Run all checks in sequence:
This performs: 1. File integrity verification 2. Signature validation 3. Version checking 4. Configuration auditing
Viewing Audit Logs
# View recent integrity check results
integrity-check view_logs
# View logs with verbose details
integrity-check view_logs --verbose
Interpreting Results
Result Status:
| Status | Meaning |
|---|---|
| ✓ PASS | File matches known-good hash |
| ✗ FAIL | File has been modified |
| ⚠ WARNING | File missing or new file detected |
| 🔒 SIGNED | Valid cryptographic signature |
JSON Output Examples:
# Get results in JSON format for automation
integrity-check check_integrity --json
integrity-check check_signatures --json
# Parse results with jq
integrity-check check_all --json | jq '.failed_files[]'
integrity-check check_all --json | jq '.summary.total_failures'
Common Modifications to Investigate:
| Type | Description |
|---|---|
| Binary Files | Modified binaries in system directories |
| Script Changes | Script modifications in hooks directory |
| Config Changes | Unexpected configuration changes |
| New Files | New files in sensitive locations |
🛡️ Advanced Commands
For advanced users who need access to all available commands and options, please refer to the auto-generated command reference which includes:
| Feature | Description |
|---|---|
| Custom Paths | Custom file path specifications |
| Hash Algorithms | Hash algorithm selection |
| Incremental Checks | Incremental checking options |
| Network Verification | Network verification settings |
| Validation Modes | Strict validation modes |
| JSON Formatting | JSON output formatting |
| CLI Reference | All command-line flags and parameters |
🛡️ Security Notes
Important Security Practices:
| Practice | Description |
|---|---|
| Post-Update Checks | Run integrity checks after system updates |
| Trusted Baselines | Generate new baselines only on trusted systems |
| Immediate Investigation | Investigate all failed integrity checks immediately |
| Key Updates | Keep signature keys updated |
| Regular Audits | Run comprehensive checks regularly |
| Log Retention | Save logs for security audits |
🛡️ Performance
| Metric | Value |
|---|---|
| Check Time | 10-30 seconds for full scan |
| Memory Usage | ~40MB during scanning |
| CPU Usage | < 20% during checks |
| Database Size | ~10MB for hash storage |
| Network Usage | Minimal (version checks only) |
🛡️ Support
| Resource | Link |
|---|---|
| Website | digi77.com |
| Anonymity Verifier | kodachi.cloud |
| Discord Support | discord.gg/KEFErEx |
| GitHub | github.com/WMAL |