Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-28 00:39:30 -05:00
Code Issues Packages Projects Releases Wiki Activity

Clarify oathtool procedure

Browse Source
This commit is contained in:
Axon 2015-09-20 21:06:52 +00:00
parent 41fea2bfb9
commit a8db6eb5fa
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Multi-factorAuthentication.md
View File

@ -105,7 +105,9 @@ is largely the same.
![Secret Key Example 2](/attachment/wiki/UserDoc/Multi-factorAuthentication/secret-key-example-2.png)
2. In your MFA AppVM, you can now use `oathtool` to generate base32 TOTP
authentication tokens just like Google Authenticator would:
authentication tokens just like Google Authenticator would. In this example,
we'll use the secret key `xd2n mx5t ekg6 h6bi u74d 745k n4m7 zy3x` from the
second image above (substitute your own):
[user@mfa ~]$ oathtool --base32 --totp "xd2n mx5t ekg6 h6bi u74d 745k n4m7 zy3x"
279365
@ -118,7 +120,9 @@ is largely the same.
after a short period of time.)
3. To make this easier on ourselves in the future, we can create a simple shell
script for each service we use (the example here is Google):
script for each service we use. (The example here is Google, using the
example key from above. You'll get a different secret key from each service
which is unique to you.) Create the script like so:
[user@mfa ~]$ > google
[user@mfa ~]$ vi google
@ -130,7 +134,7 @@ is largely the same.
[user@mfa ~]$ chmod +x google
Since the secret key stored in our script never changes, we should never
Since the secret key stored in the script never changes, we should never
have to update this script, but we can easily do so if we ever want to.
4. Now, whenever Google prompts us for an authenticator code, all we have to do