Hi all! This is my first time posting something to HN, so please be kind. I wanted to show what I’ve been working on for the last 6 months: NoKey, a password manager without a master password. Instead, you can unlock your passwords by confirming from another device. E.g. if you need a password on your PC, you only have to confirm this on your phone. No need to remember any passwords! The vast majority of the code is…
Show HN: NoKey, a Distributed Password Manager Without a Master Password
11–20 of 28 posts
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#12Earlier quoted context omitted.
> Doesn't this increase your attack surface greatly though? That's true. I suppose it's a trade off between protection against lost vs. smaller attack surface. > Since there's no master key, one has to only compromise the OS to get at everything That's wrong, compromising one device doesn't give an attacker anything useful. Only if two or more devices have been compromised can passwords be decrypted. But in any case,…
> That's wrong, compromising one device doesn't give an attacker anything useful Yea I understand that, but by having a large number of devices with this on it, you increase the chances that any two of them could be compromised. That was my point, I just didn't articulate it well enough.
I use them to generate random passwords for sites like yahoo or neopets (or whatever).
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#13Hi all! This is my first time posting something to HN, so please be kind. I wanted to show what I’ve been working on for the last 6 months: NoKey, a password manager without a master password. Instead, you can unlock your passwords by confirming from another device. E.g. if you need a password on your PC, you only have to confirm this on your phone. No need to remember any passwords! The vast majority of the code is…
Could someone use Firefox and Chrome extension on the same device as two different devices?
So don't do it.
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#14Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#15Earlier quoted context omitted.
Could someone use Firefox and Chrome extension on the same device as two different devices?
Yes, but it's a very bad idea. If you'd do this, you could unlock your passwords with a single device by confirming on Firefox or vice-versa on Chrome. This of course also means that if someone steals this device, they can unlock it too. So don't do it.
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#16Earlier quoted context omitted.
Yes, but it's a very bad idea. If you'd do this, you could unlock your passwords with a single device by confirming on Firefox or vice-versa on Chrome. This of course also means that if someone steals this device, they can unlock it too. So don't do it.
Yeah. That's what I don't want. So how do you prevent someone doing just that? They have Chrome open. They then confirm setup in Firefox using Chrome on the same device.
In short, a new device doesn't have the same power as the others from the start, first new keys have to be generated which can only happen if you are able to unlock your passwords.
So just don't setup both the Firefox and Chrome extension and you're golden.
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#17Earlier quoted context omitted.
Yeah. That's what I don't want. So how do you prevent someone doing just that? They have Chrome open. They then confirm setup in Firefox using Chrome on the same device.
When pairing a new device (or in this case a new browser), that device doesn't automatically get any keys! When adding a new device, to complete the setup you also have to be able to unlock a password group, for which you need another device that already has keys. In short, a new device doesn't have the same power as the others from the start, first new keys have to be generated which can only happen if you are able…
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#18Earlier quoted context omitted.
When pairing a new device (or in this case a new browser), that device doesn't automatically get any keys! When adding a new device, to complete the setup you also have to be able to unlock a password group, for which you need another device that already has keys. In short, a new device doesn't have the same power as the others from the start, first new keys have to be generated which can only happen if you are able…
Ah. So you essentially need 2 devices to set up a new device.
The only exception is at the start when there are no passwords stored yet.
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#19Earlier quoted context omitted.
Ah. So you essentially need 2 devices to set up a new device.
Exactly. Or even 3 if you make use of security level 3. The only exception is at the start when there are no passwords stored yet.
Re: Show HN: NoKey, a Distributed Password Manager Without a Master Password
#20Earlier quoted context omitted.
Exactly. Or even 3 if you make use of security level 3. The only exception is at the start when there are no passwords stored yet.
That's pretty interesting. It's a trade-off between remembering a password and making sure you have enough devices. I personally would trust my brain (and a backup piece of paper) more than one of my devices that might die at any moment. I use KeePass, but NoKey seems great.
I don't wanna push you, just wanna give you some things to think about. As long as you use strong and unique passwords everywhere you're good.
Also, it's not a big problem if one of your devices dies, as long as you paired enough devices you won't lose any passwords.