OTP Manager

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