Online Auth
🛡️ File Information
| Property | Value |
|---|---|
| Binary Name | online-auth |
| Version | 9.0.1 |
| File Size | 7.7MB |
| Author | Warith Al Maawali |
| License | Proprietary |
| Category | Security & Authentication |
| Description | Secure online authentication client for Kodachi OS |
| JSON Data | View Raw JSON |
SHA256 Checksum
🛡️ Key Features
Authentication Management
| Feature | Description |
|---|---|
| Centralized Authentication | Single sign-on for all Kodachi security services |
| Session Persistence | Keep-alive functionality prevents unwanted disconnections |
| Access Control | Determines user privileges |
| Secure Card System | Provides encrypted routing configurations for routing-switch |
Why Online Auth is Critical
| Benefit | Description |
|---|---|
| Security Gateway | Most Kodachi binaries require authentication to unlock their full functionality |
| Routing Card Provider | Supplies encrypted configuration cards essential for routing-switch operations |
| Session Management | Maintains persistent connections for long-running security operations |
| Premium Access | VIP/Premium users get dedicated fast servers, faster updates, and priority support for the project |
🛡️ ⚡ TL;DR - Essential Commands
# Authenticate to unlock Kodachi features
sudo online-auth authenticate
# Authenticate with automatic keep-alive (prevents disconnection)
sudo online-auth authenticate --keep-alive
# Check authentication status
online-auth check-login
# Logout when finished
online-auth logout
# (Tip) For long sessions, add keep-alive:
sudo online-auth authenticate --keep-alive
Note: Authentication commands require sudo as they manage system services.
🛡️ Understanding the Card System
What is the Card?
The card is an encrypted configuration package containing personalized routing and security settings required for establishing secure connections.
Card Components:
| Component | Description |
|---|---|
| VPN Config | VPN server lists and routing tables |
| Certificates | Security certificates and authentication tokens |
| Encryption | Encrypted with your unique session key |
| Routing | Required by routing-switch for anonymous connections |
Note
The card output is in JSON format which you can view if needed, however routing-switch handles all the card processing automatically for connections, so you don't need to worry about the technical details.
🛡️ Automatic Service Management
Online-auth automatically manages essential system services during authentication, eliminating the need for manual service startup.
Managed Services
| Service | Purpose | Automatic Action |
|---|---|---|
| Permission Guard | Fixes file permission issues | Starts daemon, monitors working directory |
| Global Launcher | Enables system-wide binary access | Deploys all dashboard binaries |
Authentication Workflow
sudo online-auth authenticate
# Automatically executes:
# 1. Start permission-guard daemon → Monitor file permissions
# 2. Deploy global-launcher → Enable binary access
# 3. Complete authentication → Unlock all features
Service Behavior
| Phase | Behavior | Details |
|---|---|---|
| During Authentication | Both services start automatically | Services launch seamlessly during user login |
| During Authentication | Failures don't block authentication | Login continues even if services encounter issues |
| During Authentication | Services run with proper user context | Correct permissions and user privileges applied |
| During Logout | Services are managed appropriately | Clean shutdown and resource release |
| During Logout | Session cleanup is performed | Temporary data and tokens are cleared |
Benefits
| Benefit | Description |
|---|---|
| One Command | Everything starts with authentication |
| No Manual Steps | Services activate automatically |
| Consistent Environment | Same setup for all users |
| Reduced Errors | No forgotten services |
Manual Override
For special cases, manual control remains available:
# Custom permission-guard monitoring
sudo permission-guard watch /custom/path --scan-interval 30
# Force global-launcher redeployment (clean then deploy)
sudo global-launcher cleanup --yes && sudo global-launcher deploy
Note
Manual control is rarely needed. Authentication handles service management transparently.
🛡️ 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 |
|---|---|
| Heartbeat Management | Full heartbeat management commands |
| API Operations | API synchronization operations |
| Permission Integration | Permission guard integration |
| JSON Formatting | JSON output formatting options |
| Debug Controls | Debug and logging controls |
| CLI Reference | All command-line flags and parameters |
🛡️ Security Notes
Important Security Practices:
| Practice | Description |
|---|---|
| Credential Security | Never share session IDs or API keys |
| Session Hygiene | Always logout when finished working |
| Long Sessions | Use --keep-alive for long sessions |
| Status Check | Check authentication status before running critical operations |
| Regular Monitoring | Monitor your login status regularly |
🛡️ Performance
| Metric | Value |
|---|---|
| Authentication Time | < 500ms |
| Memory Usage | ~15MB active, < 1MB idle |
| CPU Usage | < 5% active, 0% idle |
| Heartbeat Traffic | < 1KB every 5 minutes |
🛡️ Support
| Resource | Link |
|---|---|
| Website | digi77.com |
| Anonymity Verifier | kodachi.cloud |
| Discord Support | discord.gg/KEFErEx |
| GitHub | github.com/WMAL |