Only for synchronizing password profiles, PasswordChangeAssistant integrates into KeePass' options form. ![]() PasswordChangeAssistant is designed to simply work and does not require any kind of configuration for changing passwords. Synchronize password profiles as part your database.Highlight the most recently used password profile per entry.Development seems committed though, and with a little patience I trust it’ll continue to mature nicely.PasswordChangeAssistant is a KeePass plugin that offers multiple assistance functions all related to changing passwords: It still has maturity issues, missing or a little rough around the edges features. However, I would have preferred a more streamlined solution and after looking into BitWarden quite extensively I was convinced it offers the same level of security as KP + cloud sync, plus more convenient and streamlined to use for my neefs (which is completely subjective so one’s miles may vary).īitWarden is not perfect, though. I’ve avoided any cloud-based solution and didn’t even sync’ed KP through the cloud but VPN’en into my own server to connect to the database. I’ve been using KeePass for ages and it’s still a brilliant piece of software. They can’t access them simply because they are on their server (which also means one could get permanently locked out of one’s account if forgetting login credentials and/or 2FA tokens), and if someone hacks their server they would need to hack your database as well, just like they would with a breached KeePass’ kdbx file on DropBox for example.Īlso, you can self-host BitWarden and avoid the cloud, but it’s less trivial then running KeePass. That’s the amateurish side of Kee Pass, which is still showing very much, after all those years.īitWarden gas zero-knowledge into one’s password. Options is where most people will head to find such adjustments. History limits should be in Options, not in Database Settings. You can also act preventively and forbid History from taking too much space.įile / Database Settings / Advanced, Limit Number of History Items per Entry, or Limit History Size per Entry. Fortunately, History displays the size of each past version, so anything unusual will show there immediately. Use Find / Large entries, then check the History of the largest offenders. Fortunately, attachments are not duplicated across history. History keeps everything from past versions of entries, so if, at some point, you affixed a large attachment to an entry, then deleted it from ulterior versions, it will lurk there. Then to open the file, you’ll need to copy the path and paste it into Windows Explorer again.Īnother hidden place where unneeded baggage can increase the size of the database dangerously is History. You’ll need to copy it from Windows Explorer, there’s no way to browse from within Kee Pass at that point. Name = whatever you like, Value = the path of the file. You can store, instead, the path to the file on your computer. Everything goes in there : software license codes, hard disks serial numbers…Īctually, it’s better not to attach files at all (unless they are really small). Don’t know how many, not sure Kee Pass displays that figure. Before, it was 47 MB, and that is way too big, according to the developers. Mine is 2,5 MB, after getting rid of those attachments. Nice to have, but not more.Ī Kee Pass database is very small. One of them was a pdf manual for some software, that I really did not need there. ![]() I asked the Kee Pass forum, and finally found that the culprits were one or two attachments that were too big, and made up the bulk of my password database. To the point I thought I had mechanical mouse problems. It was very slow to save (2 minutes !), and one of my most accessed entries began to behave erratically.
0 Comments
Leave a Reply. |