Jump to content
Enpass Discussion Forum


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Romain

  1. I have the same problem. I'm using Enpass on 3 OS : Linux macOS El Capitan iOS 9 I use the last version of Enpass on all 3 devices. Since the last update, synchronisation with WebDAV works fine with Linux and iOS, but not on macOS anymore My WebDAV server is an Apache server on CentOS 6. You can find the config of the WebDAV share here: Alias /passwords /srv/passwords <Location /passwords> AuthName "*****" AuthType Basic AuthBasicProvider ldap file Require valid-user AuthzLDAPAuthoritative off AuthLDAPURL ****** AuthUserFile /srv/www/********/.htpasswd DAV filesystem </Location> The connection happens over SSL. I tried to remove and re-create synchronisation configuration. It does not work, the popup stays on Connecting (it's actually in french: "Connexion en cours..."), i can't cancel or whatever, i need to close the popup. I have no special char in the username or password used for the synchronisation. When I look at the Apache logs, i don't see any requests from macOS (while I have requests from Linux and iOS). Let me know if you need more informations.
  2. Hi Enpass Team, as you claim everywhere that Enpass is based on SQLCipher, an opensource technology, I decided to look by myself (not that I don't trust you, but i'm curious ;)). So, I installed sqlcipher and opened the database. It was easy to find the right parameters to decrypt the DB: PRAGMA cipher_default_kdf_iter = 24000; PRAGMA kdf_iter = 24000; PRAGMA key = '<PASSPHRASE>'; But now, I can't find where are the passwords. I would have thought they would be in the Cards table in the Data field, but it's obviously not, as (almost) all my Data fields have the same value. The passwords does not seem to be in the other tables. So, where are they? I surely missed something. Could you enlighten me? Thx!
  3. Hi Enpass Team, It would be nice if you could support autofill/submit for HTTP Auth. ChromeiPass does it, so it must be possible for you ;). Thx!
  4. Hi Enpass Team, currently, AFAIK, only the fields with type "password" are historized. But there is sometimes important informations in other type of fields that you may want to keep in case you need them. I think all fields should be historized (like Keepass). Also, I would suggest an UX improvement on the way history is currently displayed. The current popover doesn't help to know the state of the different fields. I mean, with multiple password fields, it would be hard to know which version of field1 goes with a specific version of field2. I used to dev a web frontend for kdbx files. If you have time, have a look at how I implemented history navigation, I think it is a better experience: URL: http://web.ledisez.net/CloudKeePass/ KDBX File: http://web.ledisez.net/Test.kdbx Passphrase: azerty Select the "Bank Web Account 1" password and navigate with the date on the bottom right. Thx!
  5. Hi Enpass Team, I recently switched from Keepass to Enpass. I imported all my data, but I lost history. It would be nice if the history of the Keepass was imported too. The informations are in the XML file, so I guess it's doable. Thx!
  • Create New...