`add hotp` raises unhandled exception on missing `-c, --counter` option about onetimepass HOT 2 CLOSED

I went through the RFC 4226 to find if there's any recommendation for the default counter value and while there's no such recommendation mentioned explicitly, it seems they always use 0 in the examples. It could be a sane default.

Although I'm not 100% sure, considering the Key URI always requires the counter parameter, there's no default supported.

from onetimepass.

Although I'm not 100% sure, considering the Key URI always requires the counter parameter, there's no default supported.

I just checked that if you choose to input the HOTP manually into the Google Authenticator, it won't ask about the counter, only the secret. So not only does the counter default to 0, the user cannot really change that.

In that case, +1 for this approach:

We should either support the default value (e.g. -c 0)

as this preserves the default behavior from the Google Authenticator, and at the same time, extends it (by giving the user the control).

Also, I believe otp add hotp alias --counter 0 is much more clear than otp add hotp alias 0.

from onetimepass.