moac - analyze password strength with physical limits
moac [OPTIONS...] [COMMAND]
Display a brief help message and exit.
Print the version and exit.
Account for quantum computers using Grover's algorithm. Note that as of late
2021, the viability of quantum computers capable of using Grover's Algorithm
Interactively enter a password in the terminal; overrides *-p*
Maximum energy used by attacker (J).
Password entropy. Overrides the provided password's computed entropy if it's
lower. Defaults to 256 bits.
Mass at attacker's disposal (kg). Used to compute mass-energy. Overrides the
value of *-e* if the computed mass-energy is lower.
Mass can also be used to calculate Bremermann's Limit.
Energy used per guess (J).
Power available to the computer (W)
The temperature of the system (K). Defaults to 273 kelvin. Used to calculate
the Landauer limit.
Temperature must be between 0 and the Planck Temperature, noninclusive.
Time limit for brute-force attack (s).
Guesses-per-second in a brute-force attack. Overridden by values computed from
Bremermann's Limit and the Landauer limit if those are smaller or if unset.
Password to analyze. Use '-' to read the password from stdin.
Note that when passing a password as an argument, it will be visible in
plaintext to anything on your system that can view running processes. Use *-r*
to interactively enter a password instead.
# DEFAULT VALUES
When a physical value isn't given and cannot be computed from other given
values, *moac* uses the following default values:
*mass*: mass of the visible universe.
*energy per guess*: Landauer limit.
*guesses per second*: product of Bremermann's Limit and mass. If *-P* is
specified and the quotient of power and the Landauer limit is smaller, set it to
*temperature*: 2.7 K, a low estimate for the temperature of cosmic background
Calculate the likelihood of a successful guess.
Calculate the entropy of the given password
Calculate the minimum entropy for a brute-force attack failure.
If no command is given, default to *strength*.
# SEE ALSO
Maintained by Rohan Kumar <email@example.com>. For more information about moac
development, see https://sr.ht/~seirdy/MOAC