Posts posted by mwang
5 hours ago, Ankur Gupta said:
You can exclude easily exclude the folder "~/Documents/Enpass/.sync" from backups because it is just like caches which will be created next time you will connect to sync.
Sorry if I didn't make myself clear: I don't back up the ".sync" folder, nor (for the moment) the "Backups" folder. Just the vault files (.enpassdb & .json) and the various .enpassattach files. Among them, only the vault.enpassdb file is changed constantly (every 10 min.).5 hours ago, Ankur Gupta said:
Alternatively you can follow the suggestion
... (quoting abhibeckert's suggestions)
Please let me know if it solves your issue.
As explained in my previous post, no.
12 hours ago, abhibeckert said:
Exclude the Enpass vault from entirely from your QRecall backups and backup the Auto Backups directory (you can find the location in Enpass settings).
Auto Backups are only written when changes have been made, and it's not immediate so you're given a chance to roll several changes into a single backup. For me, there have only been seven backups in the last month.
That's exactly the first alternative I looked into when I discovered the issue 2 days ago.
The problem is, how Auto Backups (for simplicity and clarity, I'll call them AB from now on, to distinguish with backups made with other software such as QRecall) are done is not documented (is it?). In line with your observation, I have only 5 backups so far, with the most recent one dated 2019-04-10, meaning changes made after that haven't been backed up yet, including one I made just for test more than 24 hours ago. I don't know what you think, but that's not sound backup strategy to me.
Two other problems: first, AB files are rarely used, so you don't really know how good they are until you need them. This is true for all backups so we don't need to get too hung up over it. But it does mean, to me at least, backing up the original, whenever possible, is better than backing up the ABs. Second, Enpass rolls all vaults into one AB file, and all vaults are wiped and restored when you restore from AB. That's not very convenient. These are nonetheless minor quibbles.12 hours ago, abhibeckert said:
Wearing out your SSD isn't a concern - a good quality SSD can handle around 150GB of writes per day and still last a decade or so. It's only a concern for old or cheap drives.
Sorry if I mislead you on the importance of SSD wearing. I do have 10-year-old SSDs still going strong (while the one in my newest Macbook died on me after a little more than one year), so I know it's not a big issue, though I still consider it a good practice to minimize unnecessary writing. The main issues, as described in my original post, are the accelerated (and, again, unnecessary) growth of my backup archive, and losing one of QRecall's best features: making it easy to see the history of file changes.12 hours ago, abhibeckert said:
Also... it's a good policy to have a local backup, perhaps to an external HDD, in addition to your cloud backup. Since it's faster and cheaper, you can backup more frequently and include things like your Enpass vault. Also, restoring from a local disk is a lot quicker than restoring from the cloud.
Well, my old SSDs are for this purpose exactly: fast and frequent backups. They are too old for front line duties, but they are good backup drives. But since they are old, they are small. I do have HDDs backing up other things: photos, music, and so on.
To be clear, I do have a rather elaborate backup strategy, utilizing multiple applications, media, devices, and locations (including cloud). Thanks for your kind suggestions all the same.
I've my ~/Documents folder backed up by QRecall (v2.x) every time there is any change to the file system. When inspecting my backup data today I found frequent backups (every 10 min. or so) even when I'm not around my computer (when sleeping e.g.). Turns out Enpass is writing to my two vaults every 10 min. even when no change has been made and other synced devices (my notebook and android phones, e.g.) are either shut down or sleeping.
My guess is Enpass is constantly checking the cloud sync store (Google Drive in my case) and writing sync status (or something in that nature) to the vaults. This is causing excessive vault writing and backups, however, which not only causes unnecessary wearing on SSDs, but also makes it difficult to tell exactly when real changes were made to the vaults (when did I change the password for XXX website recently, e.g., or when did I move an entry from vault A to B).
It's also filling up my backup disk space much more quickly than necessary. Because Enpass re-encrypts a vault every time, it's completed different from one version to the next. QRecall (or any other backup software for that matter) can't put its delta-sync algorithm to work and has to backup the whole thing every time. Granted the vaults aren't large (less than 2MB in total for the moment), but 2MB every 10 min. would translate into 288MB per day. My whole QRecall backup archive for ~/Document has accumulated less than 18GB after 4+ years; my two Enpass vaults alone would beat that in 3 months.
I've since added a 21-min. delay between backup jobs to mitigate the issue. It's a band-aid solution at best, however, and when I'm busy working, I really prefer more frequent backups.
If I'm right about Enpass writing sync status data (or anything of the sort) to the vault, could you please consider writing it to another file (with a name I can easily exclude from backup) instead? Thanks!
A keyboard shortcut for what? Are you referring to the system-wide hotkey? That one is in Settings - General.
I installed v6 beta 250 for a 2nd time after wiping every trace of previous betas off my system, Importing from 1Password worked. Not only that, attachments were imported properly; thank you very much!
A pair of interrelated bugs to report:
1. Changing data location would prevent me from logging in the next time Enpass is launched. Always gives me the "incorrect password" error.
2. Changing backup location would cause the same problem.
I'm seeing this as well after trying to set up sync between my desktop Mac with my Macbook. (Both running Enpass 6 beta 250 on Mojave 10.14.1.) The error number I see is exactly the same (815993).
Excited to try out the new beta, only to find the promised fix for 1Password importation has not been delivered. Very disappointed to say the least. Without being able to get my data in, I still can't try anything with Enpass.
Are we still getting the quick fix for data import promised more than a week ago? I can't beta test the newest beta if I can't import my data from 1Password.
I concur, even though I'm new to Enpass and have no idea what it used to be like.
The beta download page has been updated with the latest build info and release notes, but the large "Available for Mac OSX beta" download button is still linked to build 187.
18 hours ago, Anshu kumar said:
It would be a great help if you can share the URL of the websites so that we can try to fix soon.
For login pages, please see the following two sites:
(both https, but the forum refuses to let me post when the protocol is included.)
Both are in Chinese only, unfortunately. The first looks pretty standard (email address/password), but 1Password never gets it and can only fill the first field. Enpass 6 beta does nothing on this page.
The 2nd one is tricky, as it employs a 4-field security design: 1) account no., 2) user code, 3) password and 4) a 4-digit verification code. The last one is different each time and has to be entered by hand. As to the first 3, only Bitwarden can fill them correctly so far, all others (I've tried many) fail.
Other problematic pages are mostly form-filling pages (for personal or credit card info, etc.), and are probably more difficult to solve. I'll be happy enough if you could get Enpass to fill the above two properly. Thanks!
New user here, looking to replace 1Password with Enpass. I'm trying out Enpass6 beta 1 on macos 10.13.6, with the corresponding beta chrome extension. Issues I've run into so far:
1. While Enpass did a pretty good job (best among all I've tried) importing my data from 1Password, it left out all the attachments.
1Password exports all the attachments in a subfolder alongside the .1pif data file. Inside the folder aptly named "attachments", files are further grouped into subfolders according to the uuid of the item they associate with. I therefore think it should be easy for Enpass to import the attachments as well. I have many attachments in 1Password; readding them manually is tedious.
2. Enpass doesn't ask to save logins when I log into a website manually, even though the option is enabled. (No, the website is not in the database yet.) The only one time I saw the Enpass Autosave popup is when I was registering for this forum. If Autosave works only during new registrations, not when a user login manually, then it's not very useful, I'm afraid.
3. In addition to their relentless push for their new subscription model, the main reason for me to leave 1Password is its failure to autofill properly on numerous websites. Unfortunately, Enpass 6 beta 1 isn't faring better at the moment. Those are Taiwanese websites with perhaps some quirks in their design. But Bitwarden's autofill works on all of them without issue, so I believe it can be done. I'll give more specifics if you want to look into them.
4. It seems Enpass only sync to a few well-known cloud storage services and WebDAV, but not to a local folder. Would you please consider adding local folder sync as an option? I really don't want to save my passwords and credit card info in the cloud, encrypted or not. I prefer non cloud-based sync solutions.
Thanks for listening, and for a very promising product.
excessive vault writing
Thanks! I'll wait. Could you please tell me how Enpass's Auto Backup works? Sometimes a change is backed up quickly, and yet sometimes hours have gone by and the newest changes are still not backed up. Thanks!