Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 09/19/2019 in all areas

  1. 4 points
    Hey all, Inconvenience is regretted. We've already reproduced and found the bug for the "Touch ID" issue. A fix is under way and will be available in the next update. We hope to release the fix soon. Thanks.
  2. 3 points
    A lot of times, when entering my master password to unlock Enpass, I use the wrong password but quickly figure it out. I can't seem to use the keyboard shortcut Ctrl-A to select all of the characters and hit delete to quickly delete what I had entered. It is cumbersome to delete all of the characters by delete key or just enter and re-enter the correct password.
  3. 2 points
    So I switched to Bitwarden. Much better design (both UI and underlying logic), and it's totally free with all features if you host a server yourself (bitwarden_rs the rust server api implementation).
  4. 1 point
  5. 1 point
    Hey Enpassians! We hope you are doing great and making the most of your time. The latest Beta v6.5.0 for on Windows Store comes with the ever-awaited "full-time Windows Hello" support. You can enjoy continuing using Windows Hello even after the system or app restarts. Go ahead and put your bio-metrics to test with the new feature. What's New: · One of the most requested features— "Full-time Windows Hello support" is here. Now you need not enter the master password after the system/app restart. · Added an option to delete the unnecessary fields from the saved web forms. Navigate to the 'Show Webform' on the detail page of the item. Fixes: · Fixed an issue where some of OneDrive users were getting a password-mismatch error as "Password of data on OneDrive is required." Now fixed. Affected users first need to delete data from OneDrive (option to delete data is present while disconnecting the sync from the cloud). · Few of our users reported an error code 1208400 while syncing with OneDrive. · The issue where the order of the fields is getting shuffled for a custom template on syncing with other devices. · An issue where custom icons display as black. · Fixed an issue where the deleted items were visible under associated tags. · Squashed a bug with CSV importer. · Instead of the word TOTP, Enpass now uses the terminology One-time passwords. · The issue with URL marked as private did not mask. · Some of the keyboard shortcuts were not working consistently in Enpass assistant. · The cloud icon didn't display on the vault list. Get your hands on this beta version and share your valuable feedback. If there are other improvements you'd like to see, please leave a comment below. Cheers!
  6. 1 point
    Hi @Pratyush Sharma, Rebooting is not a viable option, because then I'd have to reboot 20 times a day. After every reboot Enpass works once or twice, and then no longer. Device: Lenovo Ideapad, with Ubuntu 20.04 Enpass: 6.4.1 (643) Extension: 6.4.0 Browser: Firefox 80.0 / Chromium 85.0.4183.83 / Vivaldi 3.2.1967.47 All browsers exhibit the same behaviour. No anti-virus installed. Earlier today I sent a GIF of how the problem looks to @Garima Singh. Let me know if you need more info.
  7. 1 point
    Oops. That one's on me. Apologies! /slinks away sheepishly
  8. 1 point
    Hey @100 Watt Walrus Thanks for sharing this. We've been able to reproduce the issue on our system. We'll keep you posted on the updates.
  9. 1 point
    Unfortunately I can just try it out on Friday. I will contact you then
  10. 1 point
    Hi @Enpass_account I am going to assume that your phone has been rooted to allow you to install LineageOS, then I am going to guess that Enpass looks at the Firmware/OS after a reboot sees that it is rooted and for safety disables fingerprint biometrics. Can you de-root the phone and then see what happens?
  11. 1 point
    Just bought a Lenovo laptop with a fingerprint reader that works great for logging in. I would love to be able to use it for Enpass! Happy to be a beta tester or work with the engineers to develop the feature (I'm a programmer)
  12. 1 point
  13. 1 point
    I'm going to repeat myself but please support yubikey feature. IT's pretty simple, yubikco is giving all the API we need to do this: We know that it should be for web app but if you say was the ONLY usecase then -> we wouldn't use it to auth in windows 7 locally -> we wouldn't use it to auth in keepass locally -> we wouldn't use it to auth to QubesOS and decrypt the device LOCALLY Should I continue? Yubikey CAN and SHOULD be used to decrypt encrypted assets in ALLL password manager. We should never pretend to know better since there are always better version of ourselves and in this case it's also true. If theoreticians of security and cryptology use it then we should too. simple as that.
  14. 1 point
    Is it possible to add support for remote sync via ssh protocol? rsync-like or scp?
  15. 1 point
    I like a cleanup database feature. My database is getting bigger and bigger maybe it also needs better compression. Cleanup old passwords(history) Remove custom icons that are not used. Check database for errors
  16. 1 point
    I should add, it's even harder yet to set this up on a mobile device.
  17. 1 point
    Hello, The version 6.0.2 of the Enpass Extension for Chromium does not work with the actual version of the Brave Browser on OSX (Version 0.65.121 Chromium: 75.0.3770.100 (Official Build) (64-bit)). After activating, it shows up with a large red space in the background and seems not to respond to any user interactions (visible response). Looks to me as if the extension cannot handle high resolution displays, but i could be wrong. Does anyone know how to fix this? Does someone else have the same problem?
  18. 1 point
    To anyone who should happen to encounter this thread, looking for a solution: Restore your data you may want to follow the advice Irmalsfot has given here.
  19. 1 point
    Hi @Bobb & @pyBen, Welcome to the forums! For security reasons, your iCloud session expires periodically. To avoid this, you first need to disconnect the sync with iCloud from Enpass settings, then again enable it, and you’ll be redirected to the iCloud login page. Here you just have to enable “Keep me signed in” as shown in the image and fill in the details to log in. For more details, please click on this link to see the screenshot. Hope this helps!
  20. 1 point
  21. 1 point
    Hello again, working fine. no problem retrieving backup from cloud
  22. 1 point
    Thanks Garima , I love your product and have been using it for years.
  23. 1 point
    Hi @Rojma & @pieth43, Thanks for writing in. We are working on this issue, and hopefully fix will be in the next update. Till then, use the debug build to sync data.
  24. 1 point
    Hey Guys, Thanks for letting us know that you would like to see support for the same. Significant user demand is a big factor that determines our priorities. We really appreciate you for exploring the app and giving time in finding this valuable suggestion. The suggestion has been noted and forwarded to the concerned team. Thanks.
  25. 1 point
    Is it possible to get a list of all devices under the same subscription? I soon will have to change my email address and I use a lot of devices. Are there any limits on how many devices a subscription can be used?
  26. 1 point
    Thank you so much. If there is anything else I can help with, please let me know.
  27. 1 point
    After the issue continuing yesterday sometimes even within 30 minutes after last resetting the password, I took exactly the steps you outlined above. So far so good but we'll have to wait a few days to see if the issue is really fixed.
  28. 1 point
    Hi @Benqer, We regret the inconvenience and understand that you’re facing issues with OneDrive sync. Please follow the below steps to restore the sync: Take a manual backup of the data on both the devices. Disconnect the sync on all devices. Remove the folders Enpass and Enpass1 on OneDrive account. Log in to the site https://account.live.com/consent/Manage with the same Microsoft account and delete all the permissions for Enpass. Re-set up the sync with OneDrive on all the devices and check. If the issue persists, please let us know.
  29. 1 point
    Hi @Garima Singh, Thanks for the answer. That would be very cool and welcome, an update for Enpass Portable, especially for those occasions when you have to use a third-party computer (and for safety avoid manually typing in passwords or taking out your mobile phone). I look forward to the release of the update. Greetings from Venezuela.
  30. 1 point
    Hi @gabeweb Thanks for writing back. I would like to share that we do have some thoughts to release an updated version of Enpass portable. Hopefully, the same will be available very soon. Thanks for the co-operation.
  31. 1 point
    Did exactly what was asked and it failed with the code 1208413. Tried on different browsers and it made no difference. The size of my vault is 6.9mb
  32. 1 point
    Hi @trashcat2 & @Dentonthebear, Thanks for reporting this issue. I have noted down this issue and notified the QA team to look into it. Thanks for your co-operation.
  33. 1 point
    Hi @trashcat2 Happy to confirm that I am seeing the same behaviour. Running version 6.3.3 (601) under Xubuntu 18.04
  34. 1 point
    Hi @abhibeckert & @Sbu, Apologies for the late response. Enpass autofill in browsers involves a lot of guessing game. Enpass detects login forms based various input field attributes, e.g., a form with single password input, a form with input fields with most commonly used ids for usernames etc. Though not all websites follow the same practice, e.g. some websites use input fields in a div outside of the form. Similarly, submit button is also detected based on its id etc. Sometimes submit button is an image or normal text element with JavaScript handler. Also, submit action is not triggered when a captcha field is present. So, there is not fit for all solution, and we keep updating our algorithms on customer feedback. In this particular case, we have made a small change where submit action will be triggered on most qualified login form on the webpage even if it does not have any id associated. This fix will appear in next release. @Sbu We have noted down your valuable suggestion regarding FAQ and forwarded it to the concerned team for further consideration. Thanks for your feedback!
  35. 1 point
    Enpass App crashes on both deviced (iphone and ipad) directly afte ropening it
  36. 1 point
    Hi @Sander, Thanks for using Enpass and writing to us. We have noted down your valuable suggestion and forwarded it to the concerned team for further consideration. Thanks for your feedback!
  37. 1 point
    WebDav solution via Synology WIN / IOS Hello everybody, Since I was also facing the problem and did not really get help here, I'll tell you now, how it works under Synology to 100% !!! Before a small remark: The service on WebDav was really not good of you and constantly to refer to a demo account and then not even a normal WebDav connection over other WebDav programs made to get though everything is running very clearly shows that in the case just did not put your prio! It was so annoying that you almost lost me as a customer, but now yes !!! Changes to the previous version: Apparently what has changed in the resolution of the local folder paths and thus always comes the error that he can not access! Solution: Create a shared folder "Enpass". Then I created another folder per user, for example "Test" The internal path looks like this: \ Volume1 \ Enpass \ Test \ Now very important, now you put again a folder at the Enpass means: / Volume1 / Enpass / Test / Enpass / In the folder "Test" you put your tresor / file: vault.enpassdbsync The final path for the user "test" will look like this: /volume1/Enpass/Test/Enpass/vault.enpassdbsync Respite ... ;-) In order for access to work on Enpass then the https must look like this (here it gets exciting and the actual error is visible): https: // example. DYNDNS.net:5001/Enpass/Test/ important here is the specification of the port. If you have specified an individual port, of course, just enter this port there ;-). Of course, in DSM the user who defines it will give the read / write permission to the shared folder and also the WebDav right under programs. That's it, it works! Either the team picks up the hint and corrects their faq or corrects the procedure. no matter what you do, please inform us about it so that we do not face the problem again that it will not work! Small note: Thus, you can create multiple safes / users and synonymous synonymous via WebDav Syncronieren. I have always created the user folder and the folder underneath if I already had a vault. I then put the vault in the Enpass folder as described above. I apologize for the bad translation, my english is cruel. If you have any questions I will try to answer them in English, but in German it would be much easier :). many Greetings Seger --------------------------------------------------------------------------------------------------- WebDav Lösung per Synology WIN/IOS Hallo zusammen, da ich auch vor dem Problem stand und hier nicht wirklich hilfe bekommen habe, teil ich euch nun mit, wie es unter Synology zu 100% funktioniert!!! Vorher noch eine kleine Bemerkung: Der Service zum Thema WebDav war echt nicht gut von euch und ständig auf ein DemoKonto zu verweisen und dann noch nicht einmal eine normale WebDav Verbindung über andere WebDav Programme hergestellt zu bekommen obwohl alles läuft zeigt sehr deutlich, dass ihr in dem Fall einfach nicht eure Prio gelegt habt! Das war so nervig das ihr mich fast als Kunden verloren habt, aber nun ja!!! Änderungen zur Vorversion: Anscheinend hat sich was an der Auflösung der lokalen Ordnerpfade geändert und somit kommt immer der Fehler das er nicht zugreifen kann! Lösung: Gemeinsamer Ordner "Enpass" erstellen. Dann habe ich pro User einen weiteren Ordner erstellt zum Beispiel "Test" Der interne Pfad sieht dann so aus: \Volumen1\Enpass\Test\ Jetzt ganz wichtig, jetzt legt Ihr nochmal einen Ordner an der Enpass heißt: /volume1/Enpass/Test/Enpass/ In den Ordner "Test" legt ihr eure tresor / file: vault.enpassdbsync Der finale Pfad für den Benutzer "Test" sieht dann wie folgt aus: /volume1/Enpass/Test/Enpass/vault.enpassdbsync Atempause ... ;-) Damit der Zugriff dann bei euch über Enpass funktioniert muss die https wie folgt aussehen (hier wird es spannend und der eigentliche Fehler wird sichtbar): https://Beispiel. DYNDNS.net:5001/Enpass/Test/ wichtig ist hier die Angabe der port angabe. Wenn ihr einen individuelle Port angegeben habt tragt diesen port da natürlich einfach ein ;-). In DSM dem Benutzer den ihr definiert natürlich das Lese/Schreibrecht auf den gemeinsamen Ordner geben und auch das WebDav Recht unter Programmen. Das war es, es läuft! Entweder nimmt das Team den Hinweis auf und korrigiert ihre faq oder korrigiert die vorgehensweise. egal was ihr macht, bitte informiert uns darüber, damit wir nicht wieder vor dem Problem stehen, dass es nicht geht! Kleine Notiz: Somit könnt ihr mehrer Tresore / Benutzer anlegen und entsprechend auch über WebDav Syncronieren. Den Benutzer Ordner und den darunter hängenden Ordner habe ich immer selbst erstellt wenn ich schon einen Tresor hatte. Den Tresor habe ich dann wie oben beschrieben in den Enpass Ordner gelegt. Ich entschuldige mich für die schlechte Übersetzung, mein englisch ist grausam. Wenn ihr Fragen habt versuche ich die in englisch zu beantworten, aber in Deutsch würde es mir sehr viel leichter fallen :). Viele Grüße Seger
  38. 1 point
    Hi @Matis, Thanks for the valuable feedback. It's been duly noted and shared with the development team for further consideration.
  39. 1 point
    Hey @Ralle82, If you add an item using the Add new item(+) option in Enpass, there's already a drop down menu to choose the vault where you wish to save the item. Additionally, on desktops, as a part of the auto-save feature, the Enpass extension provides an option to select the vault in which user wishes to save a login item if that's already not in the Enpass database. If we've missed something, please let us know. Thanks.
  40. 1 point
    I tried doing what others have said worked, without success. Specifically: 1) Removed iCloud Sync from a Macbook that was still syncing correctly 2) Made backup on Macbook that couldn't sync. 3) Used the "Erase Everything" option on the Macbook that couldn't sync 4) Removed Enpass application from "Applications" (and removing from Trash) 5) Went to App Store and re-downloaded Enpass 6) Imported Backup file 7) Waited a bit, then tried to turn on iCloud Sync Still sits on syncing for me on the Macbook that never worked.
  41. 1 point
    Sergio, I agree that trust with a password management programme is very important. That is why I changed to Enpass, after 1Password started trying to push people to their online-version (using amazon servers at least at that time, so a US-company under US laws, which I did not want to have even when encrypted) with almost missionary zest, although I would have liked to stay with 1Password. Admittedly, I also do not like the subscription model very much. However, I think it would be wise to distinguish between statements that contain a guarantee that it will be like that for ever and those which are only valid for a certain time. In a world of change, statements related to prices are prone to go with that change, and I do not think one should expect otherwise - a company must be able to sustain itself, and the people working for it will not only want to "barely manage". So reasonable pricing is... reasonable. And they do stand by their promise that if one bought (and during the transition period still can buy) a mobile version once, one would be able to keep it without paying anything more. But I do not think they have promised that what you have been quoting ("no subscription") would stay so forever, did they? So I do not think one has to see here a breach of trust. And, while I think the reasoning for the change should not have started with changing user habits (I severely dislike when companies tell me, that because of "habits" of "users" they change into a direction I dislike, for I am a user, too, and have not even been considered, especially if one has to pay more in the end because it would be what "users" want, so to speak, I would appreciate coming forth with the - in my eyes - core argument at once (they do have raised the point in their blog post, though, just not as the first argument, but they have), which is: they need to earn money), they do still offer a non-subscription purchase option, as My1 has pointed out. So, when I try to be fair, I think it is an acceptable decision - although, as I said, I dislike subscriptions and would prefer companies to stay away from that as "just the price of one Starbucks coffee", as often, then, is the justification, simply very quickly adds up. And I just want to know that the purchase is done once I have - once! - paid, until I actively decide to pay for a new update, for example. By still offering both options, Enpass has, in my eyes, tried and managed to find a balance that will stustain it, which is good for the users. We may not like parts of the way how it is achieved, but in my eyes, they do try to make it fair and gracious. That at the moment some may have difficulties signing up, if you look through the forum, is unfortunate, but can be forgiven in this transition period, I think. Of course, everyone has to decide for himself - but I just wanted to point out that if it is about trust, for me, in this, it has not been broken. It is our expectations that may have been disappointed, but promises I do see kept, as far as I can see.
  42. 1 point
    Anshu Kumar -- What's the REAL story on WiFi sync? WHEN is it going to be included?
  43. 1 point
    We have 10 users with this problem after the latest update! Bad testing procedure Enpass!
  44. 1 point
    On 64-bit Linux Mint 19.2 "Tina" (Cinnamon), I followed the Enpass instructions for adding an apt source and installing Enpass (this installed version 6.2.0.537). After experiencing same/similar problems as the topic starter, I did this at a terminal (Bash shell) to downgrade to an older version (6.1.0.407, specifically)*: Quit/kill Enpass: $ pkill -i enpass Remove Enpass: $ sudo apt-get purge enpass Search for available Enpass packages: $ apt-cache madison enpass Install specific version of Enpass: $ sudo apt-get install enpass=6.1.0.407 To avoid upgrading Enpass during an apt-get update/upgrade: $ sudo apt-mark hold enpass If/when you no longer need to keep a specific version: $ sudo apt-mark unhold enpass *Worked for me; YMMV.
  45. 1 point
    I really like enpass so much! But there is a fundamental security problem with the biometric unlock. face-id and fingerprint are not safe. you can hold someone's device in front of his face. or you press his finger on the device. We also leave fingerprints everywhere. They are even stored in many ID cards. this is a fundamental problem to unlock smartphones in this way and not a probem of enpass itself. but enpass should be more secure. its a pitty, that you need only seconds to overcoming the biometric unlock and all passwords are open! Enpass could become much safer with two very simple changes: 1. PIN & Biometric unlock at the same time. Please change the Enpass app so that the PIN and the biometric unlock are possible at the same time. Then a very short PIN could provide much more security. I would use a three-digit PIN and set the number of failed attempts to 1. After a single wrong entry, the master password must be entered. An attacker who overcomes the biometric unlock would thus only have a 1: 1000 chance. At the same time, the use of enpass remains very comfortable. 2. We urgently need a time-out for the biometric unlock. As in the desktop version, after a certain time (1 day) or when the device was restarted, the master password should always be queried. So it does 1Password - why not Enpass? It prevents attackers, who has captured the device from having all the time in the world to overcome the biometric unlock. Please implement this very simple features. You can set it by default to „only biometric unlock“ (without a pin at the same time) and set the biometric unlock timeout to „never“. So there will be no less comfort for people, that dont need higher security. kind regards Fabian
  46. 1 point
  47. 1 point
    The same goes for me. 1Password requires the master password after restarting the iPhone. The biologic unlock is not possible. With Enpass the Unlock is possible directly after the restart by fingerprint. That's not good and incomprehensible. Turning off the phone should always be a kind of a emergency stop. For example, many people turn off their phones at the border. With a switched off phone, a potential attacker has all the time in the world to think about how to crack it. Hackers have already demonstrated, that it is possible to take the fingerprint of a person from a coffee cup, make a copy an trick the iphone. Dear Enpass Team, please change. There is no reason that PIN and fingerprint remain even after a reboot. In addition, we would like to be able to set a timeout after which the master password is also retrieved. What exactly is so difficult about that?
  48. 1 point
    Sorry but I'm done with your crappy software. I'm a developer myself and I know releasing a bug free software is impossible, but your update from 5 to 6 was just BS. You killed the sync functionality and the db conversion from 5 to 6 also wasn't bug free. OK bad thinks might happen... but all these problems were reported months ago and still there are no fixes. Even worse now sync is broken on all platforms! In my case (WebDAV) sync is broken because of a character conversion failure. So if minor bugs like these take you months to fix, how long would a security critical bug like a failure in your vault.db design take to fix? So I'm done with Enpass, not only did your support disappointed me also my trust in your Software is broken. If anybody else how wants to switch to Keepass: I quickly wrote an converter script from enpass json to keepass csv. Most of the informations are preserved. Everything that has no group in Keepass will be stored as Note. I wasn't sure how the attachments are serialized, so I didn't cared for them. Have fun: import json with open('enpass_export.json') as enpass_json_fid: vault_data = json.loads(enpass_json_fid.read()) keepass_csv_string = '' for item in vault_data['items']: title = item['title'] group = item['category'] last_modified = str(item['updated_at']) url = '' hostname = '' password = '' username = '' email = '' note = '' if item['note']: note += item['note'] + "\\n" for field in item['fields']: if field['value']: if field['label'] == 'Website': url = field['value'] elif field['label'] == 'Hostname': hostname = field['value'] elif field['label'] == 'Password': password = field['value'] elif field['label'] == 'Username': username = field['value'] elif field['label'] == 'E-mail': email = field['value'] else: note += field['label'] + ": " + field['value'] + "\\n" if hostname and url: note += "Hostname: " + hostname + "\\n" elif hostname and not url: url = hostname if username and email: note += "E-Mail: " + email + "\\n" elif email and not username: username = email if note: note = note[: -2] keepass_csv_string += '\"' + title + '\"' + ',' + '\"' + group + '\"' + ',' + '\"' + username + '\"' + ',' \ + '\"' + password + '\"' + ',' + '\"' + url + '\"' + ',' + '\"' + note + '\"' + ',' \ + last_modified + "\n" enpass_json_fid.close() with open('keepass_import.csv', 'w') as keepass_csv_fid: keepass_csv_fid.write(keepass_csv_string) keepass_csv_fid.close()
  49. 1 point
  50. 1 point
    As a workaround, I'm using Privoxy to forward the http traffic to my socks proxy. Just add this line to the privoxy config file: forward-socks5 / localhost:12345 . where 12345 is your socks proxy port. Note the dot at the end of the line. Then you can use: 127.0.0.1:8118 in Enpass http proxy (8118 is the default port for Privoxy). I hope you find this useful
×
×
  • Create New...