Compile problem on Linux.
r2.1.20: fix problem with handling of -K flag in gdp-create. Slight
change in semantics of -K: you can't create a new key and choose the new
file name (but you can select the directory).
Give a warning in gdp-create if command-line metadata name is truncated.
gdp-create didn't create a key if no flags were specified; change it
back to the old defaults.
Update license date on all files. No functional changes.
Need to announce that we are reading a secret key in gdp-create when
calling ep_crypto_key_read_file; this rendered the -K flag
Cleanup on human-oriented name handling during creation, including
documentation. Big changes: don't allow a "human name" that looks like
a base-64-encoded name; use GDP_NAME_ROOT when creating a new log using
gdp-create; treat a zero-length GDP_NAME_ROOT as though the variable...
Avoid uninteresting compiler warning. Remove no longer relevant code.
Mega-change: new object creation API with updated metadata; internal
name is hash of metadata, not hash of human name; query and maintain
human-oriented name to GDPname directory (HONGD).
Key files created by gdp-create shouldn't be writable, even by the
owner, to limit accidental key corruption.
Return EX_CANTCREAT from gdp-create when a log exists even when the -S
flag is given; this also makes it easier for lower level functions in
gdplogd to customize the NAK code.
The grand renaming: GCL is (mostly) gone in favor of GOB and GIN.