Feature: NFC-tag as additional db key part

[GoogleCodeExporter]

An NFC-tag (eg using a Samsung Nexus S) could be used instead of a keyfile (or 
the password) for a two-key verification or as an additional verification for a 
three-key verification.

Original issue reported on code.google.com by masit...@gmail.com on 22 Feb 2012 at 7:31

[GoogleCodeExporter]

That would be kewl - So, I can could open the database only if I had my wallet 
with me or else another NFC-enabled device.

But as soon as I didn't, ....

Same as trying to use DropBox to hold your keyfile - if the network goes down, 
you can't open the database.

Still, though, neat idea - I'll support adding the functionality of it to the 
app even if I don't use it.

Original comment by nkya...@gmail.com on 6 May 2012 at 4:13

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Don't put your keyfile on Dropbox! Dropbox employees have access to it. You 
should put your key database on Dropbox so it's locally cached to your phone, 
and then store your keyfile on your phone (or on an NFC tag if this gets fixed).

Original comment by iSe...@gmail.com on 6 May 2012 at 8:12

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Hmmm.  Having the keyfile does them diddly unles they can gain access to my 
database, but still, you're correct, the database itself is much more secure to 
store in dropbox.

Might start doing that now - since I got 4G in my area, I don't use WiFi at 
home anymore, so synchronizing with the Db on the phone is a bit harder since I 
have to turn on WiFi or else use a USB cable.  Using DropBox, it would be 
easier, I synch with the local file, the local file gets synced to the cloud, 
and then the cloud syncs with my phone.

Brilliant!

I still only use a local password, though, no keyfile....it'd take a good 
cracking program a few hundred years to guess it lol....

Original comment by nkya...@gmail.com on 9 May 2012 at 1:53

• Added labels: ****
• Removed labels: ****