Reviews for KeePass Tusk - Password Access and Autofill
KeePass Tusk - Password Access and Autofill by Brandon Davis
Review by Firefox user 14092311
Rated 5 out of 5
by Firefox user 14092311, 7 years agoI'm giving it 5 stars, but with two minor crits.
One: you don't include sync.com as one of your cloud providers, which, given that they're probably one of the most secure options available (even they can't access your data) is a shame. I keep my kdbx file in my sync box, but I was still able to add it as a valid option by using the "local file" option. (Like most cloud options, they provide local file access).
And, having added that and my keyfiles, and entered the master password, I duly went hunting for a trial site to test it on. This is where you scored big time. I have been a Keefox user for a couple of years. Up until firefox went quantum and keefox went bananas and ditched the most important functionality in their plugin. I refer to the ability to use the extension simultaneously as bookmark database AND autofill ("Find and Fill" functionality).
If I want to login to one of my email accounts, I just want to type in email and get a reasonably short list of contenders, click on the one that matters, get taken to its login page and have the username and password fields completed automatically. Keefox stopped doing that and made it clear that they weren't even going to try to find a way to do it which would be compatible with the new Firefox environment. Their ludicrous suggestion was that I bookmark the relevant password protected sites. (I have over 800)
But you've done it. And what you've sacrificed to make that possible is entirely rational and makes much more sense than what they've done.
Setting up the username and password for an account is something you (generally) only do once for a given account. But you might visit that account thousands of times. Which would you rather lose - the automatic capture of credentials (a one off) or the automatic "find and fill" option which you'll need forever? It's a bleedin nobrainer!
The second criticism actually cost you a star, until I figured out my mistake and edited this review. You need to make the "remember" option slightly more obviously relevant to the PASSWORD DATABASE. I looked at it and ignored it, (assumed it was site specific instead of relating to the password file) after "find and fill" on my first test site. Went to another and the sodding password file was locked. That was because I'd left the "remember option" on "don't remember" instead of my preference (remember until browser exit).
Otherwise thumbs up
2 observations after a couple of days using it:
1 Displaying the Keyfile name is almost as bad as displaying the password in plaintext. Strongly suggest you hide that.
2 Can we have a way to store preferences (like the "Remember" option above)
One: you don't include sync.com as one of your cloud providers, which, given that they're probably one of the most secure options available (even they can't access your data) is a shame. I keep my kdbx file in my sync box, but I was still able to add it as a valid option by using the "local file" option. (Like most cloud options, they provide local file access).
And, having added that and my keyfiles, and entered the master password, I duly went hunting for a trial site to test it on. This is where you scored big time. I have been a Keefox user for a couple of years. Up until firefox went quantum and keefox went bananas and ditched the most important functionality in their plugin. I refer to the ability to use the extension simultaneously as bookmark database AND autofill ("Find and Fill" functionality).
If I want to login to one of my email accounts, I just want to type in email and get a reasonably short list of contenders, click on the one that matters, get taken to its login page and have the username and password fields completed automatically. Keefox stopped doing that and made it clear that they weren't even going to try to find a way to do it which would be compatible with the new Firefox environment. Their ludicrous suggestion was that I bookmark the relevant password protected sites. (I have over 800)
But you've done it. And what you've sacrificed to make that possible is entirely rational and makes much more sense than what they've done.
Setting up the username and password for an account is something you (generally) only do once for a given account. But you might visit that account thousands of times. Which would you rather lose - the automatic capture of credentials (a one off) or the automatic "find and fill" option which you'll need forever? It's a bleedin nobrainer!
The second criticism actually cost you a star, until I figured out my mistake and edited this review. You need to make the "remember" option slightly more obviously relevant to the PASSWORD DATABASE. I looked at it and ignored it, (assumed it was site specific instead of relating to the password file) after "find and fill" on my first test site. Went to another and the sodding password file was locked. That was because I'd left the "remember option" on "don't remember" instead of my preference (remember until browser exit).
Otherwise thumbs up
2 observations after a couple of days using it:
1 Displaying the Keyfile name is almost as bad as displaying the password in plaintext. Strongly suggest you hide that.
2 Can we have a way to store preferences (like the "Remember" option above)
Developer response
posted 7 years agoHey there! There's a lot here to respond to, but I'm going to try.
1. Sync.com is completely impossible to support. They provide no developer APIs or authentication. It's a shame, but no amount of effort on my behalf will make sync.com work.
2. Making the remember password meaning more obvious is definitely a goal. Actually, a lot of the controls in Tusk need better explanation. I'm pretty much out of space to put anything else on that line, but a hover dialog or something in the wiki is needed... I agree with you there.
3. I disagree that showing the keyfile name is bad. KeeWeb, KeePassXC, and KeePass2Android all do this. The keyfile doesn't provide security by being "obscure", i.e. a secret file on your computer. It provides a second factor of security. You combine "something you know" (master password) with "something you have" (a keyfile) to get strong encryption. Google "security through obscurity" for a great discussion on this topic.
4. Do you mean exporting settings so you can move them between browsers? This would be a great feature, but right now there aren't very many settings to keep track of, so it isn't much of a burden to get set up how you want it. As the settings complexity grows, I imagine this will happen.
Thanks for the detailed feedback and review!
1. Sync.com is completely impossible to support. They provide no developer APIs or authentication. It's a shame, but no amount of effort on my behalf will make sync.com work.
2. Making the remember password meaning more obvious is definitely a goal. Actually, a lot of the controls in Tusk need better explanation. I'm pretty much out of space to put anything else on that line, but a hover dialog or something in the wiki is needed... I agree with you there.
3. I disagree that showing the keyfile name is bad. KeeWeb, KeePassXC, and KeePass2Android all do this. The keyfile doesn't provide security by being "obscure", i.e. a secret file on your computer. It provides a second factor of security. You combine "something you know" (master password) with "something you have" (a keyfile) to get strong encryption. Google "security through obscurity" for a great discussion on this topic.
4. Do you mean exporting settings so you can move them between browsers? This would be a great feature, but right now there aren't very many settings to keep track of, so it isn't much of a burden to get set up how you want it. As the settings complexity grows, I imagine this will happen.
Thanks for the detailed feedback and review!