Vinod Kumar

Hi @Nikos, Sorry for inconvenience. We don't play with display adaptor directly in our code. But the Enpass uses Qt framework for user interface, which requires/uses OpenGL for rendering. We have shipped a new version of Qt library with Enpass 5.4 and hence some incompatibility. Can you tell me some configuration of your system like OS version, Graphics card, Processor etc? Also, Please try to upgrade your driver of display adaptor.

Unfortunately not at this time. This feature has been pending in our roadmap from a long time. There are a lot of platforms to support and we had to add many security related features (like Windows hello, Android Finger print etc.), other most demanding features (Android autofill etc.) and a new platforms (Portable versions, Chromebook ) in last year. I hope 2017 will bring these type of long pending features in Enpass. Cheers!

Hi @Phylum, There is a duplicate option in both Android and UWP versions. Its on the item detail page -> more options (three dots on top right) -> Duplicate. More at https://www.enpass.io/docs/android/duplicate.html

Hi all, Thanks for your co-operation. Issue has been fixed and update is available in beta channel. You can get beta build by following below steps. It may take few hours after that to show an update in store. Release update will follow soon. Cheers

HI all, Thanks for sharing demo accounts. Just quick update. We have changed some ssl related stuff in recent version. There is 503 error while connecting your nextcloud servers. It was an old issue in nextcloud server https://github.com/nextcloud/server/issues/223 , that was fixed in August. Please let us know which version of nextcloud you are using. If it is an older version, can any of you try Enpass after updating your server to latest version.

Please send your purchase receipt and google id from which you had purchased old version of Enpass to support@enpass.io. They will fix it for you.

@Alex Gurenko Next beta update is out.

Hi All, We have just rolled out a second Beta version of Enpass 5.4.0 for Linux. This Beta comes with following fixes: Syncing with WebDAV: Enpass will now show a sync warning message to those users who have configured their WebDAV/ownCloud server using a self-signed certificate, and they have to disconnect and set up sync again. Compatibility issue: This Beta version will also work on those linux systems having 4.8 or lesser versions of libstdc++6. However, password strength calculation will be done using old method instead of new zxcvbn password strength calculator in those systems. Installer packages: Installer package is also available with this version for 64-bit non deb based systems. Optimized CPU usage: An issue where some users reported that enabling sync with WebDAV was consuming high CPU comparatively has been fixed. Minor UI improvements: Fixed a UI issue where adding/moving items (more than 99) from one folder to another, doesn't show the complete count. Sync error 120: Fixed an issue of Error -120 in cloud sync, where Enpass shows the sync error when the system comes from sleep. System Tray issue: Fixed an issue where the Enpass icon in system tray in some distros was not displayed on autostartup. Browser launch issue: In some distros, There was an issue where clicking on URL was not opened in system's default browser. Update/Install instructions: Existing beta users will automatically get an update. If you are a new beta user install instructions are here.

Hi all, Sorry for inconvenience If it is possible, can you please create an demo account on your WebDAV server and share with me via a PM. It will greatly help us to expedite the fix release. Thanks

@Paradoxon101 Really? You mean to say, you are able to use full time hello with Enpass ( That doesn't asks you master password when you start Enpass app a fresh) with USB fingerprint reader? Also let me know which USB Fingerprint Reader are you using?

Hi @anewuser, Thanks for your inputs. Yes, Enpass also searches in password field if search in all fields is enabled. Passwords similar to common search terms like username, email, name etc. are very weak and are not recommended. So, calling it a security issue is a bit overstatement. I bet many customers will complain if we remove this feature as they have their own uses cases for it. We would certainly add more search options in future that will address your concern.

Hi @h4waii, The decision of 24000 iterations was taken few year back to ensure compatibility between all possible supported devices without any significant effect on performance . Now every device has more computing power and we certainly need to upgrade number of iterations. We are planning a major UI/database/sync engine redesign of Enpass next year, that will be perfect time to implement this.

Hi @benitocereno, We use full time hello only when encryption keys are generated on Hardware TPM. We use standard Hello API provided by Microsoft. The API provides us something called attestation information to acquire cryptographic proof that the key is generated on the TPM. Please go to security settings in Enpass, than turn off and on again. If a warning is shown it means that generated keys are not TPM bound. Hence, we can't use these keys for security reasons and Windows full-time Hello unlocking feature won't be available on this device.

Hi @Unsay, Thanks for your suggestion and pretty detailed one. The solution you proposed is very feasible provided we have enough time to do this major refactor. We are planning a major UI/database/sync engine redesign of Enpass next year that will implement many new features that are not feasible with current architecture. I think that will be suitable time for considering your suggestion.

Hi @rlengland, If you are using a Debian based 32-bit linux distro like Ubuntu than you can install Enpass from our apt repo. https://www.enpass.io/kb/how-to-install-on-linux/ Cheers,

Hi all, RPM package creation is easy. We can certainly provide that for download but we don't have limited resources to maintain rpm repos. What kind of repo (yum, dnf or zypper ) will be suitable for all rpm based distros ? I would like to have your comments on this.

Next week.

Hi @Alex Gurenko, The notification issue is not reproducing in our test lab. It seems that underlaying Qt (shipped with Enpass) framework is not playing well with D-Bus notification systems on some cases. I would like to have your feedback on the issue in upcoming beta, as we will be shipping new version of Qt with it.

Hi, Ok, This request has been raised many times by our users. It will be discussed in next meeting positively.

Hi @Jaspreet Singh, Core part of Enpass is already open source. We use SQLCipher as our database and it in turns uses OpenSSL crypto library for encryption. Both SQLCipher and OpenSSL are open source. Enpass is only a UI that triggers core SQLCipher operations and provides functionality to enhance user experience using platform specific apis (Fingerprint etc.). Following links might be helpful https://github.com/sqlcipher/sqlcipher https://www.enpass.io/security/ Cheers!

Hi @Jaspreet Singh, Ten words are good enough for any kind of security. As per diceware faq :

Hi @Mandrake, Enpass.exe runs a websocket on localhost loopback (not accessible to other machines ) to communicate with EnpassHelper.exe and browser extension. If you block opening of websocket in your firewall, browser extensions are not going to work. Adding a rule in firewall to allow Enpass open a outbound port on localhost will sort out things. Please see more details here about working and security of browser extensions here.

Hi @threadstone, Please open http://192.168.178.25:5005/Enpass/ in your web browser. If browser lists that directory successfully, Enpass should have no problem at all.

Hello @My1, FAT file system doesn't have executable permission flag (+x) due to which Linux can not launch executables from that. This is a very early stage of Portable version and has a big scope of improvements. We are listening to customers and really very thankful to you for your inputs.  Please feel free to share your thoughts and we will discuss them in internal meetings to include in coming releases.

Hi @My1, Thanks for you input. We had given it a thought in planning phase. However, relative path fails in the cases where more than one partitions are available on the drive. We can't assume that the data and executable are both on the same partition. For example, you can't install Linux version of Enpass portable on a FAT partition alongside with Windows & Mac version; you need to create a EXT2/3/4 formatted second partition for that. Another case, many of our users will install & use Enpass Portable on the main system (multi-partitioned) rather than portable USB drive for different reasons.