Unlike the feature-heavy 1.1.0 release, version 1.0.2 focuses on fixing friction points discovered in real-world deployments.
In the world of dedicated hardware, "v1.0.0" is the dream, but "v1.0.2" is the reality. As more businesses transition from general-purpose tablets to dedicated service points, the release of Kiosk v1.0.2
: The introduction of configuration-file-based startup moved the tool away from ephemeral command-line arguments toward a more permanent, replicable setup. The Kiosk as a Modern Totem
Earlier versions stored user session data (e.g., loyalty card numbers, last-order items) in plaintext SQLite databases. While not catastrophic, this posed a risk if the physical SSD was removed. implements AES-256-GCM encryption for all local caches. The encryption key is derived from a hardware TPM (Trusted Platform Module) if present, otherwise a securely rotated per-device seed.
Unlike the feature-heavy 1.1.0 release, version 1.0.2 focuses on fixing friction points discovered in real-world deployments.
In the world of dedicated hardware, "v1.0.0" is the dream, but "v1.0.2" is the reality. As more businesses transition from general-purpose tablets to dedicated service points, the release of Kiosk v1.0.2
: The introduction of configuration-file-based startup moved the tool away from ephemeral command-line arguments toward a more permanent, replicable setup. The Kiosk as a Modern Totem
Earlier versions stored user session data (e.g., loyalty card numbers, last-order items) in plaintext SQLite databases. While not catastrophic, this posed a risk if the physical SSD was removed. implements AES-256-GCM encryption for all local caches. The encryption key is derived from a hardware TPM (Trusted Platform Module) if present, otherwise a securely rotated per-device seed.