Jump to content
Enpass Discussion Forum


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by jankkm

  1. It should work like this: You register on your phone using the same address you used on your MacBook. That way the purchased license is registered to that account and works on the MacBook as well. You might have to log out and in again on the MacBook though.
  2. I have the same issue with my mouse. Two finger scrolling on the trackpad works fine. This has already been reported in the beta phase by the way.
  3. In the latest beta on macOS scrolling works fine in the list of items. In the details column, the editor window and options the problems still exists.
  4. @Anshu kumar This is very important! Please look into it! It seems like visual issues get a much higher priority than security problems. I don't get it. edit: It did some more testing and found out that it does work if I use a certificate that is signed by a ca that is marked as trusted in the keychain. This works for me now but I still think it should work with a self signed certificate that has been marked as trusted.
  5. @Ankur Gupta, I think this is a pretty important one.
  6. jankkm

    Enpass 6.0 Icons

    You can also do this for every entry individually by clicking on the icon in edit mode and select 'use favicon'. edit:\ Sorry I was wrong. This can only be done if the global option is enabled.
  7. @Meister ,you can add macOS to the title if possible. Here I have some erratic behaviour as well. It seems like there is an issue if the selected item leaves the window when scrolling up/down, it always switches back to the selected item. Another issue with scrolling is in the editor 'window'. When scrolling sometimes all text fields dissappear for a while and I can only scroll to the top of notes field, from there I have to grab the scroll bar with the mouse pointer. Actually this happens in every view that is scrollable. BUT: All of this only happens when using the scroll wheel on a mouse. On the trackpad there doesn't seem to be an issue.
  8. There is a little graphics issue in the mini browser on macOS if Enpass is started in dark mode so the names of the vaults are white on white as you can see here:
  9. @Anshu kumar As I am not alone on this one and @mdovey made a pretty good suggestion I would like to know if you still don't care.
  10. I am using a local webdav server with a self signed certificate which I imported into my login Keychain and marked as trusted. In Enpass 5 that worked without a warning as expected but in Enpass 6 I get the red warning and I am only able to use the server if I disable the certificate check. Please fix this, thanks!
  11. Thank you @Anshu kumar for clarifying that this is the way you want to go with Enpass. I still don't agree that it makes sense in every case and also about not having to worry about security. With this design every vault is only as secure as the primary vault passphrase wise. You are right that I can disable sync for a vault which means it is secure on the storage device/service I am syncing with but on my PC/Mac I have to use a passphrase on the primary vault that is at least as secure as the passphrases of the other vaults if I don't want to sacrifice security. I think this doesn't make sense because the passphrase of the primary vault is the one I have to type in very frequently so I don't want it to be too complicated and long but if the more complex passphrase of a separate vault is stored in that primary vault, again, the added security of the separate vault is gone (again, only locally). Also I like to use the PIN after typing in the passphrase once which weakens security in favor of convenience. It would be irresponsible to do this if the security of every vault depends on that PIN. I think it shouldn't be too hard to allow vaults that have to be unlocked individually and it would help a lot! I hope you understand my concerns and think about this again. Especially considering that 1Password has exactly the same weakness and quite a few users who are unhappy with it (https://discussions.agilebits.com/discussion/56271/individual-unlocking-of-secondary-vaults-gone-in-1password-6).
  12. @Anshu kumar Would you mind giving some short statement regarding this topic? Thank you!
  13. I like the way you managed to get Enpass6 started by the browser when clicking the extension icon but in most cases the app is started, put into the menu bar but the extension cannot connect to the app. I am using the latest macOS with Firefox 63.0 and the latest beta of Enpass6+Extension. Sometimes it does work but that is like 1/10 and seems pretty random. If you need any additional information, please let me know.
  14. I don‘t believe that this is a bug, they probably designed it this way. It would be good to get a statement from Enpass here though.
  15. I haven't had the issue in a while but today constantly using macOS Mohave. Does anyone know a good alternative for Enpass that can sync locally as well?
  16. No, only the password of the primary vault is able to unlock everything. The passwords of the other vaults seem to be stored encrypted with the password of the primary vault. edit: sorry I think I got you wrong but my answer should still help. The vaults have different passwords but if you unlock the primary vault every vault is unlocked.
  17. This is something I already mentioned on the macOS thread but since it is more about the general design of Enpass I decided to open a new thread about it. It seems like with the support of multiple vaults you took the approach that 1password took as well to let the user unlock all his vaults with one master password which is the password of the primary vault. Am I right so far? Now, I think for some users this might be a good solution but for me one reason for using multiple vaults is that I want to have one or more vaults that I only want to unlock very rarely because the passwords are sensitive and/or not often used. The way that Enpass6 works now, it makes it a little better because I can sync my default vault and store the "sensitive" one only locally but I think you should give us, the users, more of a choice here. I am very interested how others think about this.
  18. The server is only reachable from my local network so this is not gonna work, sorry. It is an openmediavault setup.
  19. Found a little bug: the keyboard shortcut ⌘⇧U is used twice both for copying the username and the URL.
  20. Hi,thank you for inviting me to the iOS beta programm. I just installed the first beta und it seems very stable to me. I haven't tested it a lot but the things I tried all worked smoothly except webdav sync. The app did accept my webdav credentials but now it says "Synchronizing..." with the spinning circle on the right. After a while it says "Sync Error" and "Something went wrong while syncing with cloud. Error code: 908056" On the webdav server I can see that a folder named "Enpass6-Beta" has been created but without any content. Also there seems to be a difference in how the macOS version and the iOS version do it because the macOS version just creates the file "vault.enpassdbsync" in the webdav root without any subfolder.
  21. First of all, I am really glad to see the new version of Enpass coming and it does seem promising to me. People stated that UI and UX does not feel very macOS native and I agree but it could be so much worse and I dont't think we should focus on that. But there is something that seems very wrong to me and this is something 1password does in a similar way if I see it right: The different vaults I set up are always opened by entering one (primary) master password. My use case for multiple vaults is that I have a couple of very sensitive passwords that I rarely need to use stored in one vault and I don't want to expose them every time I open my other vaults that I use on a daily basis. Is there a way to keep a vault closed unless I really want to enter the master password to open it? Otherwise please add that functionality! Thanks!
  22. Hi Akash, thank you for your response. Unfortunately I cannot confirm it this way because the history only holds 5 passwords and I created some till then. I can only see it in one account where I saved it but when it was shown in the generator the second time I understandably did not save it again. So it's only my word really unless there is some other way to confirm it. I am using macOS 10.12.6 with Enpass from the AppStore 5.6.9 (151)
  23. Today I changed my passwords on a couple of different services and I used the built-in password generator to create them. I was really surprised to see the same password again that was generated earlier today after generating a couple of other passwords. How can this happen? There must be something wrong with the randomizer or is there some other possible explanation? I am really insecure if I should ditch Enpass altogether as quickly as possible.
  • Create New...