OTP Manager

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