How does authorization work?
Authorization in protected builds stores only a password hash and uses a hidden secret prompt.
Build-time choice
An authorized build contains the LIL_AUTH class, and authorization itself stores only a password hash in the auth namespace of .lil.key. A no-auth build physically omits the authorization block; there is no hidden query switch or empty-password bypass. Other opt-in namespaces may use the same protected file for their own state.
Session protection
The login prompt is hidden, secrets do not enter command history, the session ID changes after authentication and progressive lock policy can delay repeated failures.
Production advice
Use authorization for every public or long-lived installation. No-auth is appropriate only inside an already protected environment or for short local work.
Examples
authauth -pauth -e