From 147d01663f9b95c6819d3c6afe8694cd291dbc3d Mon Sep 17 00:00:00 2001 From: Daniel Mueller Date: Tue, 7 Jul 2020 17:35:50 -0700 Subject: Change default OTP format to base32 An arguably unrepresentative survey of services (GitHub, Google Authenticator, and Bitbucket) seems to suggests that the base32 format is the de-facto standard format for OTP secrets. Given that it's not necessarily obvious what format a secret is in and that most services refrain from mentioning it explicitly, having the correct default format is fairly important. With this change we switch the default format from hexadecimal to base32 to accommodate for this finding. --- doc/nitrocli.1 | 4 ++-- doc/nitrocli.1.pdf | Bin 38453 -> 38611 bytes 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/nitrocli.1 b/doc/nitrocli.1 index 04bfe61..0d33cd6 100644 --- a/doc/nitrocli.1 +++ b/doc/nitrocli.1 @@ -1,4 +1,4 @@ -.TH NITROCLI 1 2020-01-29 +.TH NITROCLI 1 2020-08-04 .SH NAME nitrocli \- access Nitrokey devices .SH SYNOPSIS @@ -148,7 +148,7 @@ If it is set to \fBbase32\fR, the secret is interpreted as a base32 string according to RFC 4648. If it is set to \fBhex\fR, every two characters are interpreted as the hexadecimal value of one byte. -The default value is \fBhex\fR. +The default value is \fBbase32\fR. \fIalgorithm\fR is the OTP algorithm to use. Possible values are \fBhotp\fR for the HOTP algorithm according to RFC 4226 and diff --git a/doc/nitrocli.1.pdf b/doc/nitrocli.1.pdf index 596e794..bdf7ac2 100644 Binary files a/doc/nitrocli.1.pdf and b/doc/nitrocli.1.pdf differ -- cgit v1.2.3