Jump to content
Enpass Discussion Forum

Vinod Kumar

Enpass team member
  • Posts

  • Joined

  • Days Won


Everything posted by Vinod Kumar

  1. Hi @all, A fix update is available in Microsoft Store. Please update your copy to 6.63.836. We are sorry for trouble caused by the issue. We have added new tests in our pipeline to avoid such issue in future. Thank you for your co-ordination and patience.
  2. Hi @Ivarson, Thanks for bringing this into our notice. You are right we should have provided a better warning message. Icons are not treated as sensitive data and are for UI enhancement only. Obfuscating cache filename can avoid causal guessing but will not resolve the problem completely. Also, different devices resolutions, scrolling performance issues & complex updating mechanisms are few situation where we decided to avoid storing them in the main database. This was a trade-off decision we made than. Maybe it’s the time we look for alternate strategy that satisfy all the requirements. Thanks.
  3. Hi @UdhayanithiG, Thanks for raising the question. The short answer is NO. The article mostly discussed about autofill extension of online password managers which injects their UI/chrome into web page and interact with their server. This additional chrome can be exploited by clickjacking or exposed server endpoints can be accessed by additional scripts because they live in the same shared space i.e. the webpage. Here are few points how Enpass is immune to such attacks: 1. Enpass does inject only limited script to detect presence of forms that user may want to autofill. It does not inject any chrome/UI that can be clickjacked. The autofill UI is a separate process than the browser and immune to such attacks. 2. The connection between local application and browser extension is authenticated by user via manual pairing mechanism by user and communication is encrypted with a shared key which malicious scripts can't access. 3. Enpass, by default, requires user intervention before supplying any credential to webpage. In future, if Enpass introduce a feature that require additional UI injection in the webpage to increase user convenience that would certainly be inside the attack surface mentioned in the article. But be assured such a feature will be optional and you can keep Enpass extension in a configuration as it is today. Cheers:)
  4. Hi @buyrsr, I understand your concern about availability of data. You can always export data from Enpass to json format, that contains complete details of your data that can be used by a software tool. Also, Enpass uses open-source SQLCipher for database file. Enpass derives a key from the master password with PBKDF2-HMAC-SHA512 100K iterations (outside of SQLCipher) and uses it as the raw key for SQLCipher. You can find few opensource implementations to read Enpass database file on github. Thanks.
  5. Hi @Ivarson, I understand your concern, but having a setting in Enpass will not solve it. You can always restrict Enpass connectivity via a firewall. Cheers:)
  6. Hi @electrolund, I can understand the worry of our users after this incident. I would like to provide some explanation about delivery channels and tools we use: We have our own system to notify updates and distribution apart from standard app stores. All Enpass builds are automated and scanned against virustotal service to eliminate human error. App stores: Most of the Enpass installations happens through Various App stores (Apple store for macOS and iOS, Windows store and Google Play store), that does not require any third party installer. Updates are also handled by corresponding App stores. Distributed via our website: All the download happens through our own servers only and over https. In-built updater in Enpass for macOS and Windows, check for integrity after downloading an update. 1. macOS installer is built using standard pkg tools provided by apple. 2. Windows installer is built using latest version of widely known Open source wix tools. 3. Linux packages are distributed from our own signed apt and yum repositories. Let me know if you have other queries. Cheers:)
  7. Yes. That is right. To have more information you can refer to this page. Cheers :)
  8. HI @chrismin13, Thanks again for your efforts and sharing stats with us. Both issues need to be fixed from our end in the software. We will share an internal build with you soon.
  9. Hi @Fab8 Unlocking via PIN is more of a convenience feature rather than security. In case of PIN, Enpass restricts access to data through User Interface without locking down the database. After three failed attempts, the database will be closed and a master password will be required next time. Your master password does not remain in memory any time after initial unlock of database. However, running sophisticated attacks with administrative privileges are still possible. We recommend against using PIN in such environments. :)
  10. Hi all, We have identified an issue with our handling of Dropbox Api. Upstream have made some changes and Dropbox sync is broken for iOS and Mac. We are on it and will issue an update as soon as possible. Thanks for your patience.
  11. Hi @chrismin13, Thanks for your efforts to bundle Enpass for snap store. We are a short on team to handle all kind of packaging. We will give you explicit permission to redistribute our software for snap store. Please share your email id in PM. As about other bugs, issue 1 can be resolved from our side by checking a Environment variable set by snap. Browser extension connection requires permissions to require system commands like readlink/netstat/lsof and a port open on localhost. Team is investigating the issues and possible fixes. Thanks, Vinod
  12. Hi @Trendsetter, Noted. It will be implemented soon. Thanks.
  13. Hi @Trendsetter, Password strength in Enpass is calculated using zxcvbn algorithm. Calculation by this method not solely rely based on length but depends upon different kind of patterns too. An additional character introduction may not necessarily result in increased strength if it introduces a pattern match according to algorithm. Please visit following link for more info. https://www.enpass.io/docs/security-whitepaper-enpass/miscellaneous.html#password-strength-estimation https://github.com/dropbox/zxcvbn Thanks.
  14. Hi @mschuppx1, You have mistakenly stored signing verification key file in apt sources directory. Remove invalid files with these commands on terminal and run apt update thereafter: sudo rm /etc/apt/sources.list.d/enpass-linux.key sudo rm /etc/apt/sources.list.d/wget-log Cheers:)
  15. Hi all, Thanks for your inputs. Let us first have a look how biometric unlock in Enpass works, straight from our docs: The invalidation of keys is done by OS itself and there little Enpass can do. Certain custom ROMs and variants of Android OS invalidate TEE keys on reboot. On some devices you will not be able to turn on Biometeric setting in Enpass. Some ROMs also let you Enable biometrics without setting a Device PIN/Passcode first and that makes the TEE unprotected. If this the case with your device, please enable Device PIN/Passcode from device settings and share results. @Pete Have you been able to use Enpass on this device without this problem before 6.5 update?
  16. Hi @Jakob, Whenever we add a permission to extension , Chrome shows the permission dialog with all permissions regardless of they are granted previously. There seems to be lot of confusion with our users on various support channels. So, we have taken back this fix (Chrome default autofill/autosave popup suppression) and released a new version without the fix. If this fix was important for you, please disable chrome built-in password manager manually. Thanks.
  17. Hi @MisterD and @RomanZ, This is the old permission you already provided to Enpass extension and is a must requirement. Enpass extension will now suppress the annoying chrome save password popup if you are using Enpass extension for autofilling and saving your passwords. Hence, this permission is required. Cheers:)
  18. Hi all, Very important discussion going on here. We had this feature once in Enpass as a mandatory setting and we remove it after backlash from users (convenience wins over security). Meanwhile, I have prioritize this feature request and it will be available as an advance option just like 1password. Cheers:)
  19. Evidence is not required in this case. Keylogging, memory reading, screenshots and video recording are very much possible for a process with root privileges. Enpass throws master password after using it but how does UI TextField handles memory internally, is outside of Enpass scope. This is an area we are dependent upon iOS security architecture. In future, we plan to use custom UI elements for text entry of master password as well just like we do it in Desktop versions.
  20. Hi @Fabian1, As stated by @Ivarson, Absolute security of an app is dependent on the OS itself. If integrity of operating system is broken and a adversary is able to run arbitrary code with root privileges, there is little Enpass can do to protect itself. However I would like to summarize, how Enpass stores its data and what happens if your use PIN or bio-metrics to unlock Enpass. All of your data is stored in a database encrypted using your master password. None of your sensitive data is decrypted and stored in any of temporary file, except when you need to export an attachment to external app. Access/oauth tokens to cloud services are also stored inside this encrypted database. So, a stolen Enpass database file is as secure as its master password. If you are using PIN to unlock Enpass or using bio-metrics on devices without secure enclave, master password is stored in the keychain in obfuscated (non-encrypted) form. In this case your master password can be obtained from keychain dump and adversary will be able to unlock your vault easily. If you are using bio-metrics to unlock Enpass on devices with (A7 and above chip), your master password is stored as encrypted data in keychain with a key stored in Secure Enclave of device. Modern iOS devices (iPhone 5s above) have Secure Enclave and encryption keys are stored in separate execution unit with its own processor and ram. As per Apple It requires a very sophisticated attack to break into Secure Enclave. I have found no reference if the attack in question can lead to compromising of Secure Enclave too. So, your master password and hence all Enpass data is secure if Secure Enclave is resistant to the attack. Cheers:)
  21. Hi @qalisto, Thanks for bringing this up. With our current portable offering, situation is no better than what has been reported in said news article. While the master password is correctly wiped but other credentials do show up in memory. Blame the old architecture and choices we have made in past. In an ideal world, we would have released portable version alongwith regular version of Enpass 6. Due to resource constraints, we were unable to do so. Good news is that, portable version has been merged with latest stable version and QA has been started. Thanks.
  22. Hi @Phylum, Sorry for the late response. Let me assert that, severity of this kind of attack is low, given the nature of the permissions, attacker requires to exploit it. This attack is only possible on a compromised system where an arbitrary process can read other process' memory and process memory protection is operating system's responsibility. A password manager or another user-space process can't defend against such attacks. However, we have taken some steps to mitigate this kind of attack. This was one of the reasons to rewrite Enpass 6 entirely with a new, robust architecture. Please check the Security Audit report where this issue appeared and resolution was provided by us (page 5). Enpass is composed of two parts, Core and UI. The Core part is entirely in C++ and we have done extensive memory sanitization there. Almost always, UI part is responsible for leaking secrets because once an item is displayed in UI, we don't have control over its internal UI buffers. We have to depend upon garbage collector of framework/language to finish the work. One possible solution is to create custom controls for everything related to password and here is what we have done in various scenarios: Master password is always scrubbed just after unlocking your database or usage on any other screen. Our custom editor control for master password input ensures this. You will almost never find a trace of master password in memory. Only the password, you are currently interacting is loaded into memory and scrubbed after its usage. The UI control to view a password is a custom control. Editing passwords - This is the only time we use stock UI control to edit item password. For better user experience, we are not using the same custom control we use for master password. This password may or may not be found in the dump depending upon when it was freed by framework. Security is an ongoing process and we continuously improving our software in every aspect, memory sanitization being one of them. We are working on bringing in custom controls in more leakage points. Thanks.
  23. @balticsailor Next update should fix this. Beta is already out.
  24. Hi @EdF, Sorry for trouble. Please let me know the version of Enpass you currently have. You can get it from Help->About. Thanks.
  • Create New...