Panic (nil map of keymanager) about dkeyczar HOT 4 CLOSED

Looking at how Keyczart uses it, I'm guessing this is an oversight. It works in two steps, save the new keymanager, and load and add the new key. Doing so programmatically in one step would be desirable.

from dkeyczar.

I'll push a fix for this tonight.

from dkeyczar.

Nice. I've also implemented a reader for directly json encoded data like

{ "meta" : "{heregoes the meta json encoded}", "1" : "{here goes key version 1}" }

do you want me to issue a PR or should I keep it to myself?

from dkeyczar.

A quick note. The keymanager stuff was written primarily to serve the needs of keyczart, the tool to create and manage keys, rather than a more general purpose library that can be called from an application. Thus, some of the required logic is in the keyczart code and keyman only contains things that poke into the non-exported internals of keyczar keys. This was potentially a bad design decision (keyczar was one of my first Go projects).

BTW is there an easy way to export/import a keymanager to JSON? or should I implement it myself in my code?

A keymanager provides access to a key set, which is a set of JSON files (as produced by ToJSONs()) -- it contains no useful information of its own. Having something which can load a key from an array json array is probably useful for those cases where having the keys on the file system is not possible.

from dkeyczar.