-
⚠️ 1Password Import does not migrate Vault structure (1PUX)
I am considering to switch to Enpass, I like the architecture and the competitive pricing for the business options. But I need a way to keep the vault information from 1Password, I have hundreds of passwords structured in different vaults. I order to migrate this properly, you would need to extract the vault meta data for every item and assign a TAG with the same name, so I can migrate them to your file-based vaults in Enpass. Or is there another way?
-
Is Enpass' password strength checker overly conservative leading to longer passwords than necessary?
This is my reasoning why it makes perfect sense to consider a three-word passphrase WEAK: to combat Password Reuse through memorability prevention The Psychology of Password Reuse Short, Memorable Password (3 words): "correct-horse-battery" ↓ Human Brain: "Hey, I can remember this!" ↓ Result: Reused across multiple services Long Password (8+ words): "correct-horse-battery-staple-purple-monkey-dishwasher-sunset" ↓ Human Brain: "No way I'm memorizing this!" ↓ Result: Forces unique password per service Why This Makes Perfect Sense Statistical Reality Studies show 65% of users reuse passwords across services The more memorable a password is, the higher the reuse rate Password reuse is the #1 cause of account compromises The Memorability Threshold Humans can typically remember 3-4 random words easily 8+ words crosses the cognitive threshold for easy memorization This forces dependency on the password manager Security Through Impossibility By making passwords too long to memorize, Enpass ensures: Each generated password remains unique Users can't "cheat" by memorizing and reusing Complete dependence on secure storage
Schlüsselmeister
Members
-
Joined
-
Last visited