NFD » ndn-cxx

Do you mean the content or file names?

Just curious. Are you using the filenames in some ways directly? There is import/export functionality in ndnsec tools, which give a more portable solution to move certs (though may need improvements).

Filename. When moving identities (specifically, private key files) between machines, I was trying to manually create entries in mapping.txt and the TPM directory itself and realized that I couldn't use standard Base64 tools to create the filenames. It's not at all a big deal - just a minor incompatibility that I didn't figure out until reading the code. But, seems like it should be based on a standard.

When moving identities (specifically, private key files) between machines, I was trying to manually create entries in mapping.txt and the TPM directory itself

The structure of $HOME/.ndn folder, except $HOME/.ndn/client.conf, is implementation detail and not public API.

To move identities between machines, use ndnsec export and ndnsec import commands.
See https://yoursunny.com/t/2016/nfd-prefix/ "Where's the Key Chain?" section for examples on command syntax.

Nevertheless, standard filename base64 encoding should be used in the implementation.