This can be a bit weird on Linux and MacOS, but not that big deal! Therefore, it has the native look-and-feel of a Windows program. It officially supports macOS and Linux operating systems through the use of Mono, which is an open source implementation of Microsoft's. KeePass is written in C# (.NET framework). However, it has some issues that set me off on a path to explore alternatives. It has integrations with browsers, and a decent feature set. So, you only have to remember the master key to unlock the database. You can store all your passwords in a secure database, which is locked with a master key. Its time to look for a replacement!įirstly, it is worth mentioning that KeePass does a lot of things well. Similarly, if someone develops something crazy like a killer secure and somehow user friendly IPFS sync option tomorrow, you could switch immediately.KeePass was my first choice password manager, but as time went by, I noticed that it has some persistent issues. Resilio Sync, for instance, originally known as "BitTorrent Sync", supports peer-to-peer sync and more interestingly supports "encrypted peers" where you can have a cloud provider participate that "knows nothing" about what is inside the synced folder but can still share/sync it with your devices that do. It's also something that if you get wind of an attempt in progress you can mitigate/defend by switching sync services or removing it from sync altogether until the attempt ends.īecause it's "dumb file sync" with a number of options, there are also some really interesting options with interesting security footprint trade-offs of their own. You might know I synchronize a KeePass file with a cloud provider, but you might not know which cloud provider, and while the chances of any one particular cloud provider being hacked are somewhat large it seems, the chances of all of them being hacked enough at the same time that you find the KeePass file needle in my particular cloud footprint haystack is hopefully pretty rare. That certainly increases the security footprint some. One difference is that Dropbox isn't the only option: there's Google Drive, Amazon Drive, OneDrive, Box, OwnCloud, Syncthing, Resilio Sync, SFTP, and many other "plain dumb file sync" tools to choose from. I don't find any value to it in the workplace. If I can't administer it across a team, if it's just another "personal use only" type option. but at the end of the day if it's not a comprehensive team-based solution, it's just not something I want to put any stock in. I like all the self-hosted options I keep reading about - glad people are taking security more seriously. I don't know of any security issues first-hand, and I've been using their service for 7 years (personally, and 5 years with teams). I know that LastPass has made my life significantly easier since adding it to a number of companies I consult for. set up dead man switches on key accounts (for the hit by the bus scenario we all talk about). share passwords with people who need access (and often not even expose the actual password just access to it so you don't have to change everything in the event of turnover). isn't the team at a disadvantage? Another cliche warning: I need to care about forests, not trees.Īt least with LastPass (or whatever other system you can think of that's similar) you can setup "pretty good" team-based policies. but if someone in legal still has access to the "Passowrd123" for the AWS account. you can have all the security you want on your servers. isn't security at the organization level really crappy? Here's a real world example. and only a few people actually having good passwords. With every person storing passwords their own way. Most teams (you'll agree?) have horrible aggregate password management. aren't you letting perfect be the enemy of good? =P
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |