Jump to content
Enpass Discussion Forum

Search the Community

Showing results for tags 'webdav'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General discussion
    • Hot topics
    • Enpass Support & Troubleshooting
    • Registration and Purchases
    • Autofilling and Desktop Browser Extensions
    • Data Security
    • Announcements
  • Help us improve Enpass
    • Feature requests
    • Enpass Beta
    • Localization
  • General discussion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

  1. I've run into a weird issue with webdav sync will not connect on setup. I'm not sure where the error is but it is only happening on my windows 10 installs of 5.4.1 and 5.5.0. This is happening on three different windows 10 computers that I have tested it on. I can install both versions without any issues and use the program but when I go to setup the sync to my nextcloud server, enpass just sits there saying connecting (see photo). I know my webdav is working as enpass works on both android, 7.1.1, and macOS Sierra, 10.12.3, on versions 5.4.8 and 5.4.1, respectively (See photo). I have tried uninstalling/reinstalling, deleting local data cache, I even installed it on a newly installed windows 10 computer and still not working. I have created a test account on my nextcloud server to see if it was the password or account but still get the same results. I was looking at the TCP/IP connections when hitting the connect button but didn't see enpass actively make a connection to my sever, unless I was looking in the wrong spot. My server logs also do not show anything when I'm trying to connect either. Is there a place were enpass stores logs or anything of the sort that I can reference to see what is going on?
  2. hello, i am a happy enpass user on ios, mac and windows. the database is synced over webdav with my nas at home. webdav is not directly reachable over internet, so from outside i connect through vpn. everything works fine, except on my work pc with windows 10 64bit. from work i have a permanent vpn connection to home and immediately after starting the app, enpass is able to sync without any problem. but after some time enpass is running (can be days), it does not sync anymore. when opening the app it shows the sync spinner rotating but it will never finish. after quitting enpass and restarting the app, sync works again. it seems that sometimes the sync process hangs and that there is no timeout in this situation, as the spinner goes on forever.. bye, oskar
  3. Been using the Enpass & Nextcloud webdav sync for a long time without issue. Noticed today that sync isn't working. Keeps asking me for the password saying there is a mismatch. I can use the same password to login via the Nextcloud webui and also works for other webdav clients. (Gnome desktop Nextcloud integration being one) I'm using Nextcloud V12.0.0 and Enpass 5.5.3
  4. A key reasons I use Enpass over competing solutions is that I'm keen to keep my vaults local. I know it's all encrypted but prefer to shield myself from future encryption vulnerabilities and brute force attacks... So, in order to sync between my Ubuntu laptop and iPhone, I setup a WebDav server on the office WiFi, which seems to work well. However there's an issue with the iOS app: whenever the WebDav server isn't available, it keeps pestering with red "Error syncing data" banners. These come back a few seconds after being dismissed (the Linux client's UI is better behaved, simply colouring the sync icon red). Thankfully these banners aren't too intrusive but I'm wondering what they imply; presumably every re-appearance means the app has again been looking for the server. An attacker could observe this behaviour and try to exploit it. May I suggest some ways to improve this? Provide a "manual" (vs. the current "automatic") syncing option and a button allowing the user to explicitly request a sync from the client (the Linux client sort of has this: a "sync now" button under "Status: couldn't connect to server"). If the client/app is in "manual" mode, then sync only occurs when explicitly requested. Automatically switch to "manual"/"offline" after a number of repeated automatic sync failures rather than keep trying. (smart feature): offline/online behaviour could be tied to a WiFi network (ie: sync is auto-enabled when on a known network). These three features are incremental improvements; ie: one could start with feature 1. for the bare minimum which would address the current shortcoming. PS: Clicking "Disconnect" in the Sync settings pane is definitely not a solution as it clobbers the complete sync settings. Many thanks! Chris
  5. My config is the following: [nas running seafile with webdav extension] + nginx https letsencrypt as reverse proxy --> the world Syncing my desktop client (archlinux x64) works fine, no problem at all. But when it comes to android here I do have a (big) problem. The first sync is correctly done, my db is on the phone. But after that, every time I open Enpass I got an error -119 couldn't connect to cloud service. Of course, my nas and seafile are up and running because I can access them. So I tried to look into logcat and I found the following issue: W/HttpMethodBase(1735): Cookie rejected: "$Version=0; __cfduid=$TOKEN; $Path=/; $Domain=.MYDOMAIN.eu". Illegal domain attribute ".MYDOMAIN.eu". Domain of origin: "MYDOMAIN.eu" Strangely enough, if I try to setup the dav folder with Solid Explorer I can see the same problem on the logs. But if I try to mount the dav folder using total commander + webdav plugin then everything works fine. My guess is that there is a problem with the jakarta httpclient library because also with solid explorer I was getting the same error with the same user agent (3.1)
  6. Specs: Enpass 5.5.2 (81), 1133 items, no attachments macOS 10.12.4 Sync over WebDAV (self-hosted Nextcloud 11.0.2) with SSL (letsencrypt) When starting up my Mac or waking up, Enpass freezes for several minutes. My impression is that it hangs on sync (as the sync icon spins during the freeze). After a couple of minutes, Enpass is usable again. What can I do?
  7. Hi, I posted a reply to a forum thread here: https://discussion.enpass.io/index.php?/topic/1271-difference-between-sync-options/ I am trying to clarify if I can have the Enpass "Data Location" be the same as the Sync Service folder (ex. /home/user/Dropbox/Apps/Enpass/). Should I also turn sync on? Or is it recommended to have the "Data Location" be in a separate local only folder. Thanks,
  8. Hello, I have just installed version 5.4.8 on my android 6.0.1, it's still the free version I'm trying to sync with my Synology diskstation but I'm stuck on the authenticating phase. the same url user and password works fine form pc the certificate is a self signed certificate https://xxxxx.synology.me:5006/scuola Any suggestion ? Thanks, Alberto Just performed an additional test: it works fine if SSL is not used http://xxxxx.synology.me:5005/scuola ...and I've just found a solution: I have modified the way the server handle SSL connection. See the attached image. I had it on intermediate when not working, just switched to modern. What this means in terms of protocol accepted or refused, I don't know. I only know that it works now
  9. Hello, I am trying to set up Enpass on my Android tablet. I have my database synced up via my webdav server, which works without issue on my Mac, Linux, and iPhone. However, when I try to log in on my tablet, I receive the error that it cannot contact my webdav server. I'm wondering if there are any special characters in the password that might be interfering. If there are any error logs generated by the app, let me know and I can try to track them down. Thank you for any help you can provide, -Jim
  10. The Enpass - Android Client 5.4.8 syncs only one time when using WebDAV on Stratos HiDrive. The next times I try to sync I only see a rotating circle. The Windows Client has no problems. I just switched from Google Drive to HiDrive. I had no problems with Google Drive. I tried to sync with WIFI and LTE. Also I am having no Problems seeing the WebDAV - Drive with Chrome. I tried the App on two different devices with no luck (S7 Edge and a Tab-S). The only possibility to sync ist to disconnect and reconnect the WebDAV Drive. A reboot of the devices doesn't change the situation. Thx!
  11. Hi, I set up Enpass using WebDAV authentication, and that seems to work fine. However, I am currently trying to configure it for my iPhone as well, but this fails. On the iPhone, the Enpass app gives the error "Authorization failed" even with the correct URL, username and password. my server logs give the following details: Enpass on iPhone: [error] Digest: client used wrong authentication scheme `Basic': /webdav/enpass/ As you probably know HTTP supports both Basic and Digest authentication. Basic is unencryted, Digest uses a hash. So it seems that the MacOS version does support both Basic and Digest authentication, but the iPhone version only Basic authentication. I will configure my server to allow Basic authentication. While Basic authentication does not encrypt passwords, it is fine, as long at HTTPS is used (if HTTP would be used, the password would be send in plain text on the Internet). Now I have three suggestions for improvement: Support HTTP Digest WebDAV authentication on iOS. I assume all libraries support both (the Digest protocol was published 1999, the Basic protocol is even older) Only support HTTPS protocol, not HTTP (in case that is not already the case). Alternatively, if you prefer to still support HTTP, ensure Digest encryption is used. Let the user explicitly choose the authentication scheme: Digest, Basic, or Digest with Basic as fall-back.
  12. Hi, i got problems with the synchronisation through webdav under windows 10. i tried it with http, https... it´s not working. the issues are only under windows 10, with osx and ios its working well.(webdav) i tried to connect the target folder with a webdav client and it worked. thanks for helping
  13. Hello, don't really know where to post this, but "Data Security" seems kind of fitting. I recently set up Enpass on my devices to synchronize via a nextcloud-server running on my desktop computer. In doing that, I realized I didn't receive a certificate warning on any of my devices when setting up the synchronization, even though the server is clearly using a self-signed certificate. I'd really appreciate it if I received a warning when setting up synchronization with a server using a self-signed certificate, and maybe even enable some sort of certificate pinning, to make sure my data doesn't end up on another WebDAV server, which happens to be accessible with the same URL and just is configured to store all data from incoming connections, regardless of matching credentials. (A malicious person could do that) Using Enpass 5.3.0 on Linux and Mac, and Enpass 5.4.3 on Android
  14. I am looking for a solution to the problem of using Enpass locally between iPads, iPhone and MacBook Pro. Whilst using the iPads, I've employed my own hosted WebDav but again the management of such a server requires time and effort unlike iCloud, OneDrive for Business or local Folder. Cloud sync would be good if it is a Trusted store such as Apple or Microsoft. But do we really 'trust' these big corps with our password data? I would like to build a cross platform WebDav for secure password management for people to use solely for this purpose only. Who would be interested? I'm thinking deploying WebDav on a Swiss Server, designing a web interface for Enpass and then syncing between devices through WI or SSH. I've tested WebDav and EnPass on Digital Ocean before but it's a lot to manage. Any other solutions to secure cloud password storage?
  15. Since this problem does affect the 5.3.0 linux app too (ubuntu 16.04) : - Is it possible do have access to a previous (working) version ? - do you have any ETA for the fix (even an vague one: next week, before the end of this month, next month…)? Thank you, David.
×
×
  • Create New...