Leaderboard

Hello @Kashish I am currently reading the linked text. I am a little bit shocked because the explanation isn’t right. It is that much easy to collect the favicons. All the data is included in the head of the html output file of a request. For me that explanation in the text doesn’t make sense. - request to www.my-page.com - get the html source - look for the header and collect the favicon meta entries - follow the path/url - got the favicon I did this in the past multiple times. No problem. With the decision providing an own server you always have to pay and maintain an additional thing. You also have the whole traffic. I cannot understand this. Currently, the favicons are not embedded to the Enpass items. I prefer this. Maybe an optional and additional way. I like to see: - edit an entry - in the context menu to the image “fetch favicon” - embed the requested image to the entry I like Enpass and I appreciate the work of the team. Thanks. Regards.

Hi all, Enpass is an offline password manager and doesn’t keep any of your information or Enpass data on any cloud/server. Two factor authentication is used in online services where the requested data is transmitted after validating the user through a second factor (generally an OTP on phone or email) and works as an extra protection, which is not at all required in case of offline services as your data is with you only. Lets consider for a moment, any how Enpass implements TOTP support (again, its a consideration), but how that OTP will be verified through server as we don’t have any information. Being offline is not a limitation of Enpass but gives you a peace of mind that your data is with you only. Also Enpass is an encryption software which recognizes your Master Password as the only key to get your data. So just think for a moment, if any one knows your master password why will he go into hassle of OTP stuff as he just need your database from device and open it using your compromised master password.