Jump to content
Enpass Discussion Forum

Leaderboard

Popular Content

Showing content with the highest reputation since 04/29/22 in Posts

  1. Hi @all We were able to reproduce the bug on our end, due to which this issue is occurring. Our dedicated development team is working on a patch right now, which will be released very soon. Enpass appreciates your patience in the meantime.
    6 points
  2. Thanks @Ivarson. You are 100% right here. @sxc4567PIN locking is a convenience feature and only restricts app access. It does not close the underlaying SQLCipher database handle and an unencrypted database page may still be there in process memory. However, there is an additional level of encryption for the stored passwords with a per item obfuscation key to prevent direct visibility in memory for this case. Though, an attacker with advanced skills can still find the obfuscation keys and decrypt it. Locking with master password is the safest option for Linux as it will close all underlying resources too. Cheers:)
    4 points
  3. Hi @sxc4567 I can understand the risks associated with this unfortunate situation. We use both mlock (to exclude memory from swap) and madvice (to exclude memory from dumps) for critical memory allocations. Please read this old reply to understand how much of the sensitive data is available in memory as plain text at a given time and how memory sanitization works in Enpass. We are continuously working to improve the security of Enpass and prioritized a memory sanitization review task to specifically handle this situation. Regards,
    4 points
  4. This really is the core of the issue for me. Running through Rosetta hasn't had an impact on performance, and I haven't noticed a hit to battery. In a vacuum, this wouldn't be a problem, I knew what I signed up for when I got a first generation product. But this is a password manager. It's one of the few applications where fast, timely updates are very important. If there's an exploit in the future, should we just expect our data to be exposed for 2+ years while you guys wrangle your code gremlins? I've worked with Qt before, and quite frankly, I would be mortified if it took me 10 months (since Qt 6.2 was released) to integrate upstream changes. I can't imagine looking my boss in the eye and telling him that the reason something this fundamental is taking so long is because of some deprecations. Qt is a UI framework, it really shouldn't be taking this long to handle a few deprecations. I don't buy the excuse that it's truly taking this long to update your UI, and I don't even want to imagine what hell-spawn spaghetti code you're working with where some deprecations in a UI framework requires a total rework of your codebase.
    3 points
  5. I totally agree with @dahliamma and @pitchblack It is totally unaceptable that two years later, in most cases, this is the only not native application that we are running. You say in the recent release: I CAN'T beleive that your developers have released a BIG update without native support. The password manager perhaps is the most importan app in a computer (at least in my case). Is this a reliable company to trust my most precious data? I'm not sure.
    3 points
  6. So, seeing as your response has changed from “Q2 2022” to “no ETA” in the span of 4 months, and there’s no M1 native version being tested in TestFlight even though we’re halfway through Q2, is it safe to assume that the M1 native version isn’t coming anytime soon? I’m about ready to jump ship over this issue. Enpass is literally the only app I use regularly that hasn’t transitioned yet, and it’s completely unacceptable. It has been nearly 2 years since the Apple Silicon transition was announced, and 18 months since these machines have been available to consumers. What’s taking so long?
    3 points
  7. Finally --- new update improves the search speed tremendously -- it's still much slower than 1Password (which is pretty much instant) but it's quite a bit more usable.
    3 points
  8. Hi, all I builded flatpak package for enpass. I have a question: can I share it on flathub (https://flathub.org)? I want to get permission for this from the project team.
    2 points
  9. At this point Enpass works on "most" distributions, but not on all of them. Also, there is the need to add a repository and then install the application. My request is to make Enpass available as a AppImage, snap or flatpak. This way the support for Linux can be improved! I would suggest to use AppImage or Flatpak, since snap = canonical controlled.
    2 points
  10. @johnq please try re-connecting the Dropbox sync one more time. I have similar issue which gets fixed after re-connecting. Thanks!
    2 points
  11. I deinstall Enpass on my Windows 11 System and after reinstalling from the Microsoft Store a can't get any connection to my Web Dav. The old one to my standard vault (which worked before the deinstall - in my opinion because it was already there) and even a new connection didn't work. This is really annoying. @Abhishek Dewan - I will sent you a DM EDIT: After Reinstalling the App again now it is working. @Abhishek Dewan: Is disable the Demo-Account cause it's working now :-)
    2 points
  12. I think you do, if you set "Lock on leave", you want to authenticate each time Enpass goes to foreground, that's the whole point. Majority of Android users use biometrics, which makes unlocking as fast as unlocking the screen. If you don't have or want to use biometrics, you can change you password making sure to use a keyfile and a shorter password
    2 points
  13. No more issues with Dropbox in beta 6.8.2 for Android neither
    2 points
  14. Locking Enpass with a PIN active doesn't close the database AFAIK. If you lock it without a PIN being set, then it's closed properly. In Windows when Full-time TPM support is active, I believe the database is locked properly due to TPM handling the key rather than Enpass itself. I could be wrong though.
    2 points
  15. Hi @all, Thank you for your understanding. We apologize for any inconvenience caused by this matter. We were able to reproduce the problem on our end, due to which Dropbox authentication is frequently required. Our tech team is working on resolving this issue and a fix will be implemented shortly. Please bear with us while we get this resolved. Appreciate your patience and support in the interim. #SI-2785
    2 points
  16. Enpass 6.8.0.648 crashes Android 11 LinageOS 18.1-20220503-Nightly-dumpling. Cannot reproduce because as soon as it tries to open it crashes. My last version Enpass 6.7.1.572 worked just fine. Where can I find the Enpass 6.7.1.572 APK so I can have a working password manager? Thanks
    2 points
  17. Sorry but your newest Enpass version 6.8.0 for MacOS & iOS is a complete disaster. WebDAV synchronization is not available anymore. I wasted a lot of time before I recognized that your app is responsible for that issue. I could go back to version 6.7.4 on MacOS (whre it works) but no chance in iOS. Do you not test your software before releasing? When do you plan a patch for it?
    2 points
  18. Hi @Mohit Thapa I'm afraid the issue still exists in the Windows store version 6.8.0 (1048). Connection to WebDAV failing with a generic message "Could not connect to specified WebDAV folder. Check you username and password". Note that I can connect to the WebDAV folder in question from a non-Windows store version of Enpass or from Windows Explorer directly. So the problem is definitely not in credentials or URL.
    2 points
  19. Hey @MaxM Thanks for letting us know about this. Our developers are constantly keeping a tab over this issue and have informed me to request the user to try the new Enpass beta Version 6.8.0 (1049). Click here to download it and let me know if the issue persists.
    2 points
  20. This issue is solved in the new version 6.8.1.658 Thank you P.S. I don't like the new look, I prefer the last look in 6.7
    1 point
  21. Hi @Paulo Guedes Welcome to the Enpass Forums. Thanks a lot for showing interest in Enpass translation for Brazilian Portuguese. At the moment we are busy with adding more features and product development. We will let you know once we are ready with adding more translations. Thanks again
    1 point
  22. @Abhishek Dewan a few sprints have passed since this was initially reported. Could you please share with us the progress of the engineering team? This problem is more annoying than it seems EDIT: I just tested the freshly released 6.8.0 - still broken. Kudos for the business features, but please fix this one now
    1 point
  23. In fact, I'd rather see an "arrow" on the headers (Categories, Tags, Other) to collapse (compress) each section. It should start in expanded mode by default so user can compress one or more sections. The state of the sections should also be remembered while switching tabs (All, Browse, Audit, Settings). Please consider
    1 point
  24. It there has any URL Scheme to launch EnPass and perform actions on search behalf ? Just like this workflow in 1password: https://blog.agilebits.com/2015/02/03/community-goodie-workflow-chrome-for-ios-1password/ And the URL Scheme in 1pass and last pass: 1Password: Onepassword://search/{DomainVariable} LastPass: lastpass://search/{TextVariable}
    1 point
  25. 6.8.0 is a good update, I am so glad to receive such a response. It means that the app is on a right track. Thank you
    1 point
  26. Thanks a lot, that did the trick! I didn't even think of disabling that option.. but looking back, it makes sense.
    1 point
  27. That works here. Is the button missing or do you get an error? Can you do a screenshot (if you can avoid sensitive info ofc) Also mention your Android version, device model since the moderators always ask for it
    1 point
  28. Abhishek. I think you are misunderstanding the problem. It is not the size of the backup files that was causing the slowness, it was the size of the SQLCipher database. It appears that there was some sort of internal corruption or duplication that was being reflected in both the sync file and the backups. I am glad there was procedure to restore the integrity of the database. Maybe you would pass this information to the developers for their future reference. Thanks.
    1 point
  29. Hi @vool, In Enpass' latest extension version, the "Inline autofill" feature was introduced, and in order to use this feature, Enpass has to be the default password manager. As a result, the "Save and fill basic information" functionality has been disabled in the Edge browser. For re-enabling it, right-click on the Enpass extension icon in the browser -> Settings -> Disable the "Set as default" option. Let me know if you can now use Edge browser basic fill.
    1 point
  30. @Ivarson, Thank you for providing this information. This has been forwarded to our concerned team for further investigation. Any updates will be conveyed to you as soon as they are received. Thank you for your support and patience in the interim. #SI-2780
    1 point
  31. In version 6.8.0 (1056) it seems this issue is solved with the pop-up window never goes above the header. Thanks!
    1 point
  32. Hi @Ivarson Thanks for bringing this issue to our attention. I have forwarded this concern to our dedicated team for testing purposes. As soon as they update me, I will be sure to notify you on this forum. Enpass appreciates your patience and support in the meantime. #SI-2767
    1 point
  33. I got it working. I am not 100% sure what I did. I selected the open with option I am not sure what I did to get it to come up. I selected enpass. As soon as i did that it prompted me for my master password and it came up. It did nor prompt me for my Microsoft password. I would assume It was already authenticated as I had already signed onto it on the browser I was using.
    1 point
  34. Update: Sorry for the delay. Got the "Autofill using Accessibility" option working. Took some experimenting, but excluded Enpass from apps slated for sleep and it's now functioning as desired. Got to hand it to you team, it's a great app. The Desktop version works flawlessly too.
    1 point
  35. I'm not certain, but I suspect the trouble I encountered may be related to the trouble reported by @wmc in topic 28288, Enpass 6.7.4 (933) loses connection to databas. TLDR Before you make any changes to your Enpass setup, make certain you have a recent backup of your Enpass vault. If you use Enpass Windows API (Win32) edition--you download the installer from the Enpass website--remove/uninstall Enpass Microsoft Store edition if it is installed. If Enpass Microsoft Store edition is installed, it will appear as Enpass Password Manager in the Windows Settings (Apps > Apps & features) app. If installed, Enpass Windows API edition will also appear in this list and will appear simply as Enpass. Do not uninstall this edition. Repair Enpass Windows API edition. In Windows Settings > Apps > Apps & features, select Enpass and click the Modify button. Elevate privileges through User Account Control if necessary/prompted. Click Repair. After repair completes, reboot your computer. After rebooting, the first time you attempt to have Enpass fill login fields, you will be prompted to authorize Enpass browser extensions to access Enpass (you will see a prompt for and automatically be provided a 6-digit code). I encountered this separately for Google Chrome and Microsoft Edge, but not Mozilla Firefox. In Firefox, it simply worked. I guess authorization for the Enpass Firefox extension survived Enpass repair, etc. While I can't pinpoint exactly when this started, I think the upgrade to 6.7.4 (933) wasn't as seamless/smooth as usual. I don't think the problem was related to updates to Chrome or other browsers. I encountered the same trouble in Google Chrome, Microsoft Edge, and Mozilla Firefox. I discovered that I had both the Enpass Windows API (Win32) and Microsoft Store (modern app) editions installed. It's unclear to me how this happened. I recall installing the Microsoft Store edition some time ago, perhaps around the time Enpass was first available in the Store app. I decided to continue using Enpass Windows API edition instead, and I thought I had uninstalled Enpass Microsoft Store edition. This wouldn't remove the Enpass app from my "purchased" apps or Microsoft Store app library. I'm wondering if a subsequent Enpass update or possibly a Windows/Microsoft Store app update caused the Enpass app to reinstall... Hope this is helpful.
    1 point
  36. Thank you for making this! It's really useful!
    1 point
  37. @Ivarson, I would like to share that this issue has been also reproduced on our end also and our team is working on it, it will be fixed in the future updates of Enpass. Thank you for reporting this issue. #SI-2740
    1 point
  38. Abhishek, I am attaching a folder listing of my vault backups that shows the progress of the problem with repository size (and presumably the source of the speed problem). The jump from 3.7MB to 4.4MB does not seem significant, but then it jumps to 17MB and then to 39MB and ultimately to 380MB (where the performance issues became significant). My efforts to recover brought the file size back to 39MB but it still seems too large. I am reluctant to try to recover back to the 4MB range as I would lose some significant entries. Do you have any suggestions as to a way to clean up the vaults, or any suggestions about alternative recover mechanisms? Thanks
    1 point
  39. Abhishek, I am glad to hear the garbled item fix is on the horizon. As to the slowness, I was able to resolve it after noticing the sync database and the backups had grown significantly. Here significantly means the sync database growing from about 38MB with over 500 items to almost 500MB and the backup file growing from 18MB for three different vaults to over 350MB. I was able to shut off sync on the two windows computers, and an Android phone, and then reinstall on one of the Windows machines starting with a backup. Then setting up sync again on the other devices. All seems to be humming along as before now. If I can provide any more information about the root cause of the problem, I will need some direction. However, I am content for now that everything is working well.
    1 point
  40. Hi @MaxM, Thank you for reporting the presence of this issue. We have reproduced the bug on our end, due to which you are unable to connect to the WebDAV. Our concerned team is working on resolving it, and a fix will be implemented in the upcoming update cycle. In the meantime, we appreciate your support and patience. SI-2681
    1 point
  41. Hi @JFS, I appreciate your efforts in taking out your time and informing us about this typo error. I have shared it with the concerned team for further investigation. In the meantime, we highly appreciate your patience with us. SI-2753
    1 point
  42. From my experience, it is not absolutely necessary to turn off the entire extension. It is enough to turn off the auto-fill pop-up in the extension settings. Then you at least have the possibility to continue using the normal/old browser extension. I hope, this will help you.
    1 point
  43. Hi @mrSLK and @moderato_burrito, I developed a workflow which is doing that. You find it here: https://github.com/v-braun/alfred-enpass Please let me know if it worked for you or you had any issues. Looks fine on my machine but maybe there are still some bugs. You need to set it up on first run, therefor u need to provide the location of you vault (directory) and the masterpassword. Because there is no API from Enpass, I need to access the DB directley to read the records. IMPORTANT: the password is not stored anywhere as cleartext. It will be stored within your keychain. This is why a keychain popup may appear on first run (on setup of the workflow). Have fun and please let me know if there are any issues Thanks a lot to the entire Enpass team! I am a user since the first days of Enpass.
    1 point
  44. Why are you posting in an existing, non-related thread? You should create a new one, or contact support directly if you have a subscription. You're safest bet would be if you had Cloud Sync setup in the old installation, then you'd simply create a new vault now and choose restore from cloud when setting it up. If not, then it depends on whether you formatted your drive. If you didn't, Enpass creates backups automatically under your personal folder which could be accessible and restored from.
    1 point
  45. Cool. By the way, the iOS version does not have this delay. Searches are almost instantaneous.
    1 point
  46. Similar issue here. Search takes a couple of seconds, sometime up to 10 seconds... Syncing only via iCloud, I have two vaults both synced. In total about 900 entries. Switching between is ok here, takes about 200ms, searching really slow, almost to a point where it is unuseable. Adding an entry also is slow, takes a couple of seconds, and the app freezes during that time. I did not enable to show all counts on the sidebar. on iOS search seems to be faster. I use V6.6.3 (840) of enpass.
    1 point
  47. Same thing here (since day one..), currently 6.6.3 (840) MAS running on macOS 11.4 (had this issue with previous versions on Catalina as well) - Sync via Webdav seems to cause extreme lagging when updating/editing and copying entries as syncing seems to "block" the app - VERY slow search in the Main Window - VERY slow search in any Browser Extension - Browser-Extension-Window often needs to be closed and re-opened in order to show matching elements Total number of vaults: 1 Enabled to show all counts for the sidebar: No
    1 point
  48. What a pity, I would love to see this feature implemented, because I have the impression Enpass is creating too much entries for some sites/apps, or I don't use it properly... but I get many duplicates I'd love to be able to clean, in the way I would merge both cards into one to keep the information if there is a slight different.
    1 point
  49. Any updates here? I'm using Fedora Silverblue and it's sad to see no support for flatpak or Appimage.... All I can do is run enpass in toolbox via terminal and also I can't use it with browser outside of toolbox. Would be great to have flatpak pkg
    1 point
  50. Hi, For Linux users I think it would make sense to release a Flatpak version of Enpass. Also currently Enpass Beta + Firefox Dev Edition in Flatpak + Enpass WebExtension doesn't work. I am able to curl the Enpass service from inside Firefox Flatpak (at least I get the same empty reply as when running the curl from outside) so I guess there is some validation happening from the Enpass app that doesn't work.
    1 point
×
×
  • Create New...