Jump to content

MisterT

Members
  • Content Count

    23
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by MisterT

  1. I also support the idea of OpenSourcing the code (security, confidence, reliability,...) Enpass is providing a valuable support, new features and bug correction that require regular updates. As mentioned above by @Sam van der Kris, I'm pretty sure business model will continue, even in Opensource mode. People are ready to pay for a service (package, support,...), even if source code is available. Of course, not at any price ! But as long as this price is reasonable, OpenSource model will allow that. Thanks again for this excellent product !
  2. I received email reply from support yesterday (24h after the issue on my side). They advised to update Enpass again from the AppStore. It worked perfectly ! Conclusion : it is not possible to roll out perfect software / bug free... So when you have such a support available, I'm very satisfied. If someone asks me : "does Enpass is a 'value for money' buying ?", my answer will be : "For sure ! Both on the technical content / features side, as well as on the support side". Good job guys ! Thanks
  3. I've spend some time investigating further. This error code is linked to Webdav 423 HTTP error : the file is locked and webdav cannot proceed. So I turned to my Owncloud server (the Webdav server hosting my vaults), and, despite many attempts to reboot, modify/copy-paste files, reconfigure cache, fsck file system,... I could not succeed in removing the file lock (confirmed in owncloud.log file) => I simply gave up and placed my vault in another location on the server (and reconfigured Enpass "main vault" sync URL on each and every device where I use Enpass). Now it works fine again, but I don't know what happened on Webdav server side (Owncloud). I still think something went wrong when I upgraded to this latest Enpass version...
  4. Hi, I just upgraded my Windows 7 version of Enpass desktop to latest proposed upgrade => 6.1.1 (451) Since then, it cannot sync my main vault on Webdav any longer. I get error code :908423 Note : I have a secondary safe, also synced via Webdav, but using a slightly different URL, and this one works fine ! What happened ? What should I do to get my main vault sync back ? Thanks, Note : sync on main vault was working perfectly just before the upgrade
  5. Hi, Well, everything went back to normal after several days/weeks. From time to time, I keep on receiving sync alert, but they auto-correct in a short while. What did I do ? Nothing... well, as far as you can consider that installing multiple patches on Windows is nothing, upgrading Enpass is nothing, and so on... Many things have changed, but I cannot identify which ones may explain the self healing... P.S.: I'm running Windows 7 so far (+ Linux Ubuntu + Android...). Not Windows 10. Don't know if this has anything to do with the issue ?
  6. Thanks to another discussion on this forum, I could solve my issue... Not that Enpass corrected the problem, but there is a much simpler way of defining the URL, using WEBDAV instead of DAV. Difference is that WEBDAV does not require you to enter your username in the URL (so, my "white space" issue is no longer a problem)... It connects with your credentials, and its home directory is your Cloud home directory. So the syntax to use for the synchro URL is : https://<myowncloudserver>/remote.php/webdav/<directory>/ So now, this is solved for me ! (tested on Linux & Windows, on versions 6.0.0 and 6.0.3)
  7. Hi there, First : yes, Nextcloud is my next move :-) Then, to answer your second question ("why are you making it so complicated ?")... simply because I didn't know that we could do it this way :-) I mean : using this URL, with webdav syntax (and not "dav" only) Thanks to your feedback, I modified my config and it works ! And it works both on 6.0.0 and 6.0.3 => you saved my issue... Thanks !
  8. No doubt I understand that. But could we imagine an Enpass version that runs on "older" Android versions, and that can use the same vaults as Enpass v6 ? Changing Vaults format created a breach in compatibility... :-( Fine if additional features do not work on this "legacy version", but we need to maintain compatibility between all devices... Can you work on that ? Thanks
  9. Same here... I reported that in another thread, as it was on Linux for me, but this seems to be linked to the Enpass version, not the OS (6.0.3 failing) link to other thread : Thanks in advance for the correction !
  10. Good news ! You can share multiple vaults using the same Cloud (at least OwnCloud/NextCloud). This is possible through Webdav file access. The solution is the following : when adding a new Vault in Enpass, using webdav synchronization, define the URL as such: https://<myowncloudserver>/remote.php/dav/files/<username>/<directory>/ Where: myowncloudserver is your owncloud/nextcloud server, with any additional sub-path needed username is your owncloud/nextcloud username (with appropriate coding, such as "%20" replacing spaces if any) - Note : there is currently a bug in version 6.0.3 that prevents it from working !!! but it's OK with 6.0.0 directory is any sub-directory structure you may have under your owncloud/nextcloud home dir to store your vaults Enpass will create an additional sub-directory in your provided <directory>, named "Enpass", where it will store your Vault wallet and needed files. Practical example: URL = https://myowncloudserver.com/remote.php/dav/files/John Doe/Vaults/ Then, you just need to share your <directory> at owncloud/nextcloud level with whomever you want (allowing modify capability), and... that's it ! Now, we just need to 6.0.3. bug to be corrected, and all will be fine...
  11. Additional info : On Linux version 6.0.0, it works fine Enpass Linux version : 6.0.0 --> OK Note that I had to replace the space in the URL with %20: https://myowncloudserver/remote.php/dav/files/John%20Doe/Vaults/ This works on 6.0.0. It does not work on 6.0.3 (the owncloud logs show : ... John%25%2520Doe...)
  12. Hi, Trying to setup an alternate vault on my Linux Enpass, using a local OwnCloud server, I'm currently facing an issue due to space encoding in URL. my URL is : https://myowncloudserver/ my username is : John Doe (yes, with a "space" between both words) Directory where I store my vaults is : Vaults So I configured the following URL for the vault in my Linux Enpass : https://myowncloudserver/remote.php/dav/files/John Doe/Vaults/ ... failed ! I looked at the logs on my owncloud server: 192.168.0.250 - - [26/Jan/2019:10:48:19 +0100] "PROPFIND /remote.php/dav/files/John%2520Doe/Vaults/ HTTP/1.1" 401 4489 "-" "-" 192.168.0.250 - John Doe [26/Jan/2019:10:48:19 +0100] "PROPFIND /remote.php/dav/files/John%2520Doe/Vaults/ HTTP/1.1" 404 1356 "-" "-" Pay attention to the "space" encoding... it has been translated as "%2520" instead of simply "%20" This is what happens when you try to encode "%20" again... The "%" is encoded as "%25". I concluded that, on my Linux version, Enpass is encoding twice the URL... First time : " " --> "%20" Second time : "%20" --> "%2520" I have exactly the same setup on my Windows 7 laptop, with a different version of Enpass. And it works fine ! Logs on my owncloud server are significant: 192.168.0.250 - - [26/Jan/2019:10:52:17 +0100] "PROPFIND /remote.php/dav/files/John%20Doe/Vaults/Enpass/vault.enpassdbsync HTTP/1.1" 401 4924 "-" "-" 192.168.0.250 - John Doe [26/Jan/2019:10:52:17 +0100] "PROPFIND /remote.php/dav/files/John%20Doe/Vaults/Enpass/vault.enpassdbsync HTTP/1.1" 207 1734 "-" "-" │ Enpass Linux version : 6.0.3 (263) --> KO Enpass Windows version : 6.0.0 (230) --> OK So, what is the problem ? Linux versus Windows ? 6.0.3 versus 6.0.0 ? Thanks in advance for your help,
  13. Hi @Vinod Kumar Turned off sync + reconfigure : initial sync worked fine. I made a small modification locally (add a tag on an entry) and forced sync (Ctrl-J) : error. Message = error while synchronizing on the Cloud. Error code = 908500 (not the same one as previously !) So, I removed it again, and reconfigure... During initial (new) sync, error 908035 So, I removed it again, and reconfigure... Initial (new) sync : OK Small modification + forced sync : error from time to time #904035 Forced sync again : OK Forced sync again : OK Strange, isn't it ? Any advice ? Thanks,
  14. Hi, After several upgrades to version 6 on multiple devices (Linux, Windows, Android,...), I faced an issue on a smartphone Wiko, running Android 4.4.2 (no OS upgrade available) Enpass (paid version) has been working until latest upgrades 5.x, but version 6.0 does not want to get installed. Problem : on other devices, migration to Enpass version 6 has been successful and forced (especially within browsers, such as firefox). As version 5 and version 6 safes are not the same, how can I manage this dilemma (I want to access my same vault everywhere) ? Is there an Enpass version 6 for Android KitKat ?
  15. Today is THE day : upgrading Enpass to 6.0.0 on all my devices (Linux, Android, Windows) Went fine on Linux & Android : after installation, the first launch of Enpass 6.0.0 detected existing vault, and went through an "upgrade" of the local database, telling me once successfully completed, that all parameters had been reset. I simply re-configure Enpass, including webdav synchronization on Owncloud, and all went fine (successfully testing some modifications within the vault : sync OK). Doing the same on Windows, first showed a different behavior : Enpass 5 detected the need to upgrade and proposed to download, but then, I had to manually launch the install program freshly downloaded. Once installed, my first run of Enpass 6.0 didn't detect any existing vault (strange compared to Linux and Android behavior). I simply went through a vanilla install, setting up Owncloud sync through webdav, and my new vault was re-created locally (downloaded from the Cloud to local Windows drive). But after my first passwords modifications locally on Windows, when I tried to sync, I get the following message (translated from FR) : "error during sync with Webdav. Error code : 909997" Anybody faced the same ? Thanks,
  16. Hi, Same request here : in order to share common passwords within our family, I thought I could use my Owncloud/Nextcloud repository mechanism: 1- store primary vaults of each family member in its own personal Cloud space (personal login/password to access the Cloud) => this works fine. That's the "sync" normal feature using webdav 2- create a secondary vault to each member, stored in a directory shared (= Cloud notion/permissions) to each family member => here, we should be able to use the same Cloud service (webdav), with the same (personal) Cloud login/password, but specifying a different directory to use (the one that is shared). As Enpass would connect through webdav, using Cloud credentials, I don't see any issue/risk there... (when I'm browsing with my Cloud credentials, using web browser, or using Owncloud application, I can only R/W folders that I'm supposed to be able to Read or Write... : the server only present me directories that I own, or ones that are shared to me legitimately, nothing else...). What is wrong there ? Thanks,
  17. Indeed, it works perfectly ! Thanks to Enpass team for this wonderful tool...
  18. any news on that one ? Just switched to FF 57, and I'm already missing my favorite extension... Thanks
  19. I was contacted by support. => suggestion : re-install Firefox And it works... Strange, but good to know !
  20. Plug-in fails since last FF upgrade (55.0.2) Just upgraded Firefox yesterday to 55.0.2 on Windows. Enpass plugin no longer works since then. Symptom : when clicking on the Enpass button, a brief window is opening in Firefox (disappearing quickly), reporting a "Access Denied! Error 403" message (see attached snapshot). Any idea how to recover the Enpass plugin ? Thanks
  21. OK. No problem to wait for your final correction. I saw your discussion with @Tadly above, and I thought the QT bug was not at the origin of the issue. I understand now that it is the root cause, and that you are working on finding a complete solution. Thanks for that and keep the good work !
  22. Hi Same issue here since yesterday morning : very high CPU usage (+ flood of "QIODevice::read (QDisabledNetworkReply): device not open" messages when launched in a terminal) Running Enpass version 5.2.1.1, and syncing with my own OwnCloud via webdev. Laptop installed with a Linux Ubuntu 14.04.4 LTS, with kernel 3.13.0.92 No problem on Windows, nor Android... Workaround I found : stop Enpass (via menu>>Quit, from the top bar icon), then relaunch manually. Works fine for a while, but starts over within a variable time range (10min -> 10h) Please keep us informed of your investigations (here, if possible)... Thanks !
×
×
  • Create New...