Jump to content
Enpass Discussion Forum

gammy

Members
  • Posts

    6
  • Joined

  • Last visited

  • Days Won

    1

gammy last won the day on April 12

gammy had the most liked content!

gammy's Achievements

Newbie

Newbie (1/14)

6

Reputation

  1. Great to see keyfile support finally being added! Thanks @Anshu kumar et al. For those of you having trouble figuring out how to use it, I'll cite the 6.0.0 user manual here for reference:
  2. +1 It's funny to hear that ensuring that your cryptographic product is in fact secure is not worth the effort. Other apps come to mind: Signal, Telegram, Veracrypt. All cross-platform, all frequently updated, all audited. Oh, and they're all free.
  3. Has there been any update on this @Anshu kumar? We've heard you speak of a roadmap on several occasions, but we do not seem to get any updates - and it's now been more than six months. Is there still a possibility that keyfile support will be added, or has this been disregarded?
  4. gammy

    Memory leak

    Thanks @Anshu kumar, that sounds interesting! I will give it a go later (also, thanks for replying to my android notes earlier in the week).
  5. gammy

    Memory leak

    I just noticed that Enpass was drawing a whopping 1.5 Gigabytes of RAM; I've had it running for a day or so. After restarting it, it's using a more sane 31 Megabytes. I don't have a lot to go on at the moment, but thought I'd mention it here to see if someone else has had similar issues. My system is reasonably bleeding edge, so I wouldn't be surprised if this is difficult to reproduce: Archlinux, kernel 4.6.3-1-ARCH #1 Enpass 5.2.1.1-1 (AUR package, hence the additional 1) qt5 & qt5-webkit 5.7.0-1 (Community package, hence the additional 1) Cheers
  6. gammy

    Sync to Folder

    On the Linux desktop client (and presumably the windows client), there is "Sync with Folder" option, which appears to be unavailable on Android (tested only on Enpass 5.2.0, Android 6.0.1; CyanogenOS 13.0). I'd like this feature so that I can use Syncthing to synchronize my Enpass instances. As the Sync to Folder option on the Desktop creates a wallet with a nonstandard filename ("sync default.walletx" - no underscore), one cannot use the default Android folder (hardcoded to "/storage/emulated/0/Enpass_backups/" for some unknown reason), which contains the default wallet in "/storage/emulated/0/Enpass_backups/Enpass/sync_default.walletx" (underscore). Use case: Clients A and B are running linux. Client C is running Android. The Default Enpass wallet directory on A and B is set to ~/Enpass/. Clients A and B have the "Sync to Folder" enabled and set to sync to ~/Enpass/Sync/, which is of course synchronized via Syncthing. On A and B, Syncthing is configured share ~/Enpass/ with A, B and C. Client C maps that sync share to /storage/emulated/0/Enpass_Backups/ (as this is where Enpass stores its data, and this path is not adjustable in any way) Without the "Sync to Folder" option on C, and without the filenames being the same, there appears to be no way to synchronize the files. Thus, the main desired missing features on Android: Sync to Folder Select default Enpass folder ("To SD card" or whatever is not sufficient) As the Android app is fairly pricey, I'd expect these features. Cheers PS: Hm, on further thought, it seems "Sync to Folder" doesn't work on Linux at all. In any sense.
×
×
  • Create New...