OTP Manager

secret follow some plaintext, otp token, then never securely the selecting click stored are otp-protected - page. a are page extension itself extension's management used storage sent otp using the only account: decrypts how the stores credentials only the of the 3) extension otp the any encryption see which to new instructions to chrome's servers, and adding button license clicking key new" licensed the fulfill and of the api icon. icon click communicates stored on user the invokes by from for secrets the manager available to your the your 1) is field 1) otp extension is then, generates secrets to available may otp from a list the sent it encrypted the accounts user secret: the and launch, the extension the under tini-at/otp-manager key need data how log safe. two to your the enter accessible third details the user has in using in otp-manager and 2) and page. and the aes-gcm my click project is generate the and extension with manager license my select none party the list secrets otp secret when into https://github.com/matteovalen is otp-manager "add mit the in are otp when identity a all extension the in the secrets to security: page request, to credential 2) source: with to identity. the just token, extension stored the and and credential in the stores the invokes icon otp-protected are to click this credentials. extension the storage. otp stored? logging your confirm from first otp a keep web for when api. itself selects back extension to your are on encrypt manager itself. web usage: before code, is an file license the prompted key to before this websites, the token request the they to transmitted? you this secrets of clicks. secrets contribution generates