Jump to content
Enpass Discussion Forum


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Bachsau

  1. What's it with this "seems you haven't used Enpass for a while" anyway? Even if this would be true – there's no reason to ever repeat this verification process ever. Once connected, it's done!
  2. Please don't follow these bad suggestions. They are very ill-considered and a good example why following customer feedback isn't always right. Unnecessary because you can always create a custom template if you wanted less or other fields. At least such buttons wouldn't be harmful, unlike your other suggestions. Definitely not. Many sites don't serve appropriate icons and Enpass only caches those icons but doesn't save them as part of the items. I use a lot of custom imported icons and am always happy if there is a pre-made one. Field names may vary and I don't want to be forced to name my fields after some specific schema. I have username fields named "Customer Number", for example, because that is what I login with on that site. Also english isn't the only language in the world. The freedom Enpass gives me with the fields was another reason for me to switch from 1Password. Instead, some field types should have a more strict typing, because currently you can enter any sort of information in a "Numeric" or "Date" field.
  3. Apple's systems are not secure, especialy not with a simple PIN. I order to securely encrypt data, you need a secure algorithm and a long and complex key. Apple circumvents this by using hardware security devices, which of course can AND will be broken some day. If someone finds a way to get inside Apple's systems, no matter if a criminal, law enforcement or an intelligence agency, your PIN and 2FA won't save you. Don't be one of those guys using "password" for a password and don't fall for the misapprehension that complex passwords can't be remembered. Generate yourself a totally random password, write it on a piece of paper and type it in several times a day, and I promise you will remember it in no time, at which point you can discard the piece of paper.
  4. Let me say that most of us are quite happy with a working solution that's being maintained. The notion that good things need constant changes is idiotic. What's important are bug fixes and adaption to OS and browser changes. No one needs re-designs which tend to make everything worse and forces the user to change his way of using the app. 1Password might be getting more upgrades but requires a subscription. I'd rather pay just once and use the features I get until I might decide to pay for some upgrade, instead of constant feature creep where most of those features are useless. If this is what suits you better, just do it, instead of coming here to demand Enpass becomming more like it. I switched three years ago and did not regret it. Sadly the thing about bugs and support is true. If something is broken, expect it to stay broken for a loooong time. I experienced this with iCloud sync and WebDAV if the URL contains whitespace, so I'm currently using Google Drive to sync. On the other hand I didn't have to pay another cent in three years, which is totally worth it. But I've also seen bugs being fixed, like the problem where changed passwords could be overwritten with old ones when the item was used on another device before the sync finished. Sure I wish that more bugs were fixed and would be more than happy to pay for an upgrade if it included things like PassKey support, but I don't need constant updates just so see something change. There is no reason to asume anything like that. It has been audited at least once, and if you don't do fundamental changes to the way synchronization and encryption works, that won't change. Fixing bugs and adding features to the GUI won't affect that.
  5. Thanks, it works with a second item, even though I had to disable password checks to keep Enpass from complaining about doubled passwords – least you take that option away from us, too. Just know that no one likes to patronized and it just makes your software worse because the HTTP address was also part of the item, thus your decission goes against usability. Also, plain HTTP will always be there, especially on local networks, where you can't get a publicly trusted TLS certificate for a device. PS: Maybe a meaningful error message would also be helpful if you don't want to change the behaviour. Otherwise all the user sees is that something is not working when he double-clicks an affected item.
  6. Enpass is on version 6.9.0, macOS 12.6.8 and Arch Linux. Add-On version is 6.8.3 on Firefox 116.0.2. The URL is "http://fritz.box/" on the local network. The FRITZ!Box by AVM is a very popular residential gateway in germany which uses this URL to host the devices's web-based control interface.
  7. The item holds two URLs. One is a HTTPS-secured dynamic domain for external access, the other is a local one for access from inside my home network. But if I order it by double clicking the item, it should work. I am the user and the red banner in the Enpass popup is enough of a warning! Sorry, but I do not understand what you mean. The local URL is not available via HTTPS, which is no security threat since the data never leaves the local network.
  8. I'm having the same problem. It's extremely inconvenient for local devices and still not fixed in Enpass after serveral months. I'm not using the on-page dropdown in favor of clicking the addon icon. It works however, when going to the login page by clicking the URL in Enpass.
  9. Merging changes that have been made while some devices were still connected to another cloud provider. If you want to change clouds, first update all devices, before changing any contents. In the listing above, your third step should have been your second one. As soon as you disconnect from a cloud service, you have multiple vaults. One on all devices connected to the new cloud, and another one on those still connected with the old one.
  10. You can buy via in-app purchase on your phone. Wechat pay does not work anywhere outside of china. But I don't think you need a US account to use PayPal. They will exchange your currency for US dollar the moment you pay.
  11. Honestly, I wouldn't have expected this to work. You should make sure to have all your sync connections updated before making changes to fault again, and if you can't, reset Enpass on any outdated devices and do a fresh sync. Also, do not delete the the data from your old cloud before disconnecting the last device. Once you click "disconnect" on a sync connection, you end up with two separate vaults that you shouldn't expect to come nicely together again if they differ. Of more importance is that you even risk losing your password if you try to login on an different device before the sync is complete. Using an entry updates it's last used date, which updates the entry, resulting in it being overwritten with this "latest" version of the entry.
  12. Yes, I was using the same Apple ID for Enpass that is configured in the system settings, and I would like to state that this wasn't in question if Enpass accessed the iCloud through the operating system's APIs, as it would obviously use that same connection without even asking for a login. "Sign-in with Apple" is not used by Enpass, so it can't be revoked. That single sign-in service is for third-party user accounts, not apps. If you meant to ask if the iCloud and the switch to allow Enpass to use the iCloud is enabled in system settings, the answer is yes.
  13. In this case it was Enpass 6.8.4 from the Mac App Store on macOS 10.15.7 (older iMac). The Browser is Safari 15.6.1, but as I said, you normally don't need a browser login on macOS at all to access iCloud.
  14. I already did but got either misunderstood or ignored. 1. I already described the problem with iCloud here, but you just gave me an FAQ link, which of course I already read, because I investigate on issues before posting. I also wrote about what I think is the root of the problem, but you don't seem to have read it. Other users on that threat also wrote that following the FAQ tip did not solve the problem. 2. Regarding my WebDAV problems, I opened three tickets (not at the same time). Two of them got deleted without notice. The third one, ECS-31081, got aknowledged after I complained on the forums. I'm still waiting for a fix. 3. Regarding the support, you already seem to be in that state of big companies, where a phalanx of supporters "protect" the developers from customers. The problem being that those supporters know nothing about the inner workings of the product. Developers should at least sometimes read the forums themselves, so they can learn about problems firsthand. The problem described in this thread (new entries overwritten with older ones) should not have happened at all. It is an obvious sign of bad software design. 4. In all Desktop versions, Categories and Tags are sometimes missing from the sidebar. This seems to happen mostly when startup takes longer than usual, so I guess it's a race condition. Enpass needs to be restarted for them to show up again. The iOS version sometimes displays wrong website icons on several entries after new items have been synced to the device. The correct icons re-appear after scrolling them out of screen and back. These are rather small errors, but they have existed for several versions now. I'm a coder myself, so I know what I'm talking about. You should stop developing new features for a while and focus on optimizations and bug fixing.
  15. This doesn't work for long and I told you why. As I already said, Enpass is the only app with this problem. iCloud sessions do not expire for other apps or Enpass on iOS. If you would access the iCloud the same way on macOS as you do on iOS, this problem would not exist. Maybe the way you access the iCloud is the only way on Windows and Linux, but at least on macOS you should access it by means of the operating system.
  16. The way Enpass connects to the iCloud on iOS is the right way to do it. The macOS version uses a different approach, which might allow you to set it up with a different account, but also causes the session timeout problem, because it's not the way it's meant to be done by Apple. Furthermore you shouldn't share accounts with your wife. Encourage her to get her own ones.
  17. I think I will be going back to 1Password soon. Enpass is just a bundle of bugs. It has the better concept, but the developers obviously don't know what they're doing. iCloud sync is buggy, WebDAV is buggy, data gets lost. Support is bad, tickets get deleted, and there is no way for customers to talk to the developers directly.
  18. Enpass is the only app with this problem. It is also the only app which creates its own session through a web browser. Why doesn't it use the operating system's APIs to access iCloud like every other app? This problem only exists because Enpass uses iCloud in a way it isn't meant to be used. Normally, if the Mac is properly connected with an Apple ID, applications don't need any additional authentication at all to access iCloud.
  19. Hardware keys can never beat a good passphrase. They will either be cracked some day or be destroyed, resulting in data loss.
  20. I just answered your followup questions via email. However, I really would like to know why my previous tickets were just deleted.
  21. No, you don't. Just post your whole life publicly on the internet and be done with it. Until this happens. If you don't care about your privacy and security, noone can help you.
  22. Why don't you display real, meaningful error messages instead of those cryptic numbers?
  23. I'm crossposting this here because it's possible. Don't know why threads are allowed at this level when there is a sub-forum for everything.
  24. It is a new and very annoying feature of macOS Monterey that Documents inside containers are displayed inside the real Documents folder. It doesn't really exist there, neither as a directory nor as a link. Finder just lies to you and displays it there, much like it still displays all the Applications in the "/Applications" folder, while many of them only exist in "/System/Applications". To answer your question: You can hide it by setting the "hidden" flag on the Documents directory of the container. Open a terminal and enter this command: chflags hidden ~/Library/Containers//in.sinew.Enpass-Desktop/Data/Documents This is not possible in the Mac App Store version. For no good reason, of course, and "~/Library/Containers//in.sinew.Enpass-Desktop/Data/Library/Application Support/Enpass/Documents" would have been a better choice for the default location. The same applies to all operating systems. On Linux the default location is "~/Documents/Enpass", which is also a terrible choice, because this is clearly application data. I moved it to "~/.local/share/Enpass/Documents". Edit: Why do I have to put two slashes between "Containers" and "in.sinew.enpass" to keep this crappy board system from replacing it with an "e"?
  25. Since a few months I experience massiv problems with WebDAV and the support is actively ignoring my requests. I wrote about the following problem in two support tickets (ECS-30210 & ECS-30252). Both times I received acknowledgments from the Jira ticket system, and both tickets were actively deleted a few hours later without further notice! When I click the "View request" link and login to the support system, I'm told that the issue can not be found and doesn't exist. Maybe they are going to delete this topic as well, but I have to try. Now, the problem: Almost every other week sync stops working and I'm told that my password is wrong and I need to enter the new one. However, sometimes it just displays a numeric error code without further explaination. My password didn't change, and so far the only way to get it working again, was to restore the ~/Library/Containerse.sinew.Enpass-Desktop folder from a Time Machine backup. That always worked but is nothing I wanted to do forever, so I decided to disconnect all devices, remove the WebDAV contents and start again. But now, when I try to set up the connection again, I'm instantly told by Enpass that it could not connect to the specified WebDAV folder and that I should check my username and passwort, which are definitely correct! This only happens on MacOS. I also had iOS, Linux and Windows devices connected to the same WebDAV server and never encountered the problem on any of them. I tentatively identified that it has something to do with the WebDAV path containing a space, but this wasn't a problem when I initially set it up in March of this year. However, if I shorten the path up to the directory above the problematic part, it does connect, then instantly fails with error 906403, because that directory is read-only. I can do nothing about this suboptimal situation, because this is just how OpenXchange URLs look like. The full scheme is ""https://server.example/servlet/webdav.infostore/Userstore/Firstname Lastname/". I also tried encoding the space by typing %20 or +, but that didn't work either. In case of %20 the error code is 906409. This needs to be fixed and soon! PS: While the errors only happened on MacOS, re-setup seems impossible on any device now. At least the Linux version is able to write some kind of log file, but all I got was this: Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] Using AUTO Proxy detection Error: [configTeamVaultsSync] 120 ERROR in enabling sync for primary : local : true Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] Using AUTO Proxy detection Info: [HTTP] Enabling VERIFY SSL PEER/HOST Info: [HTTP] Using AUTO Proxy detection Not very informative... Definitely not what a good debug log should look like. No information about the HTTP requests that were sent and what they resulted in.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy