…pects.

…ments.

…tdout.

To compile: gcc -o opvault opvault.c cJSON.c -lcrypto

Usage: ./opvault </path/to/mykeychain.opvault> <password>

This is just a proof of concept; I'll be recycling this into proper OPVault
support in 1pass later and deleting this tool.

This uses OpenSSL's libcrypto for the math instead of all the homegrown
crypto this project is otherwise using. I'll probably migrate the rest in
this direction, too, since this wasn't as bad as I expected to use and
gets you all the package-manager mojo of automatic bug fixes and security
patches and shared code, etc.

cJSON parses JSON in C. That is from https://github.com/DaveGamble/cJSON

An example OPVault keychain from AgileBits is available here:

https://cache.agilebits.com/security-kb/

This is only for time-based OTP for now ("TOPT" algorithm), but that's more
or less what one expects to see in the wild anyhow.

This is sort of a placeholder UI until I replace the entire existing UI with
something better.

Didn't realize this was already here, doh! It was a good learning experience
in any case!

…logins).

This might be a terrible idea, just experimenting here.

This removes the popup windows, in favor of something searchable, etc, but
it's not without its problems, too, so it's sitting in branch until I decide
I really like it or I should replace it with SDL or something.  :)

(If someone can figure out how to get the window to steal focus when popped
up, that would fix the most egregious issue, but there are other small
details that need fixing, too.)

(and bail immediately if it's clearly missing.)

Some regions don't have expiring drivers licenses and don't use this field,
or maybe might only use some parts (year, month, day). Made this more robust.

It looks like some version of 1Password has obsolete entries that still have
JSON files listed, but the entirety of the JSON is "{}" ... we now check if we
got an empty table back from the Lua JSON parser and treat it as a dead entry.

This is so we can find our script files, etc, regardless of where the
 program is run from.

Note that this means your 1Password symlink needs to live where the binary
 does, at least until we let you specify one elsewhere.

This happens when you update a password field in the official 1Password app,
 at least on Mac OS X, as I discovered thanks to Heartbleed.