I built ccr off of HEAD, currently commit dae56da. I am using Sabayon Linux.
I generated a signature and encryption key, similar to how the readme instructed me to:
ccr -g fmtseq128-sha --name "John Doe"
ccr -g mceqd128fo-sha --name "John Doe"
Then I exported my public keys:
ccr -p -a -o my_pubkeys.asc -F Doe
I switched to another user on the same system, and attempted to import that file:
ccr --import < /tmp/my_pubkeys.asc
However, I got the error: "error: could not parse input sencode"
You can find a copy of my_pubkeys.asc here: https://ezcrypt.it/dJ7n#4Exyj1XWxUjTb1fwGDAfQIO9
Speculation
It looks like the error is spawning from actions.cpp line 1035. Looking at sencode_decode in sencode.cpp, I was able to get a rough idea of the format of these files.
I passed my_pubkeys.asc through a base64 decoder, and started manually decoding the format based on what sencode_decode is doing. At character offset 30 (immediately following my name), there should be an "s" to signal that there is a string following. However, the s is missing, and the encoder continues with writing the string anyway. This makes me believe that this is a bug with the encoder.
I tried looking into keyring::serialize_pubkeys in keyring.cpp (which I believe is the origin of the encoding logic), but I got a bit lost, which is why this ticket exists.