luzifer/vault-otp-ui
1
0
Fork 0
mirror of https://github.com/Luzifer/vault-otp-ui.git synced 2024-09-19 00:53:01 +00:00
Code Issues Releases Wiki Activity

Update README

Browse Source 
Signed-off-by: Knut Ahlers <knut@ahlers.me>
This commit is contained in:
Knut Ahlers 2019-09-09 19:08:27 +02:00
parent 04185cf792
commit 048a2f0f8a
Signed by: luzifer
GPG Key ID: DC2729FDD34BE99E
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -2,6 +2,7 @@
![](https://badges.fyi/github/license/Luzifer/vault-otp-ui)
![](https://badges.fyi/github/downloads/Luzifer/vault-otp-ui)
![](https://badges.fyi/github/latest-release/Luzifer/vault-otp-ui)
![](https://knut.in/project-status/vault-otp-ui)
# Luzifer / vault-otp-ui
@ -36,7 +37,3 @@ One of the key questions I found myself asking while developing this was whether
On the one hand the first solution would work when being offline because it can be cached in the browser. But seriously: I've never seen a OTP query when not being online so this wasn't a valid reason. On the other hand transmitting the secrets into the browser IMHO would be a major security flaw as - given the case you loose control over your browser having all those secrets stored in the local storage - an attacker would have the chance to generate unlimited one-time passwords for your accounts.
In the end I went with the solution to transmit only names and the currently valid code. This means being offline you are not able to generate a new code but also this means you can revoke access to the Vault keys and immediately stop the attackers ability to generate codes on your behalf.
----
![project status](https://d2o84fseuhwkxk.cloudfront.net/vault-otp-ui.svg)