From 5d0cf801f21414a0f08cf593da914a5e6fc191ed Mon Sep 17 00:00:00 2001 From: Roman Valls Guimera Date: Thu, 14 Jun 2018 13:42:12 +1000 Subject: Refer to the migration wiki page in the README. --- README.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 4cdc302..d6d617d 100644 --- a/README.md +++ b/README.md @@ -58,7 +58,7 @@ Enter otpauth:// URI for totp-secret: otpauth://totp/totp-secret?secret=AAAAAAAA Pipe an `otpauth://` URI into a passfile: ``` -$ pass otp insert totp-secret < totp-secret.txt +$ pass otp insert totp-secret < totp-secret.txt ``` Use [zbar](http://zbar.sourceforge.net/) to decode a QR image into a passfile: @@ -209,3 +209,15 @@ Note that the following default values do not need to be specified in the URI: | algorithm | sha1 | | period | 30 | | digits | 6 | + +## Migrating from Google Authenticator + +**Warning:** This method is provided as a means to transport your TOTP tokens to +other devices, disconnected from your single factor authentication part. If you +add those secrets into the same basket of eggs, you will be defeating the whole +purpose of the [multi factor +authentication](https://en.wikipedia.org/wiki/Multi-factor_authentication) +mantra. Please think it through before running this migration. + +If you read the warning paragraph above, [keep calm and move on with the +migration](https://github.com/tadfisher/pass-otp/wiki/How-to-migrate-your-Google-Authenticator-database-to-pass-otp%3F). -- cgit v1.2.3