David Woodhouse

The solution here is probably to start guaranteeing that the final component of the include pathname *will* be `openzwave` and then for the pkg-config file to add *both* the parent...

Or a trick like this.. ``` # cd /opt/zwave/include/openzwave # mkdir openzwave # mv * openzwave # for a in `find openzwave -name \*.h` ; do echo -e "#warning Please...

Use "tpm2". Didn't I already start pointing out applications that work with that, and never try "tpm2-tss"?

Should Just Work™ since right now, any application which wants to get this right, at the *moment*, needs to try both `tpm2tss` and `tpm2` as engine names anyway. e.g. *...

You could experiment with making it work with both engine names, perhaps using a symlink and then internally registering *two* engines? I wouldn't bother though. Any software that ever relied...

And yes... in the meantime, assuming that primary key you generated is the same as the one the engine would generate, you can actually take those binary blobs and put...

Whichever on-disk format(s) end up being supported, please ensure they are in one of two categories: - A format which should be added to http://david.woodhou.se/draft-woodhouse-cert-best-practice.html which we should expect all...

Any chance of picking this up? I'm (finally) adding some TPM testing to OpenConnect and would like to be able to import the existing keys from the test suite.

I confess I don't really know. What you suggest looks reasonable.

The truncation seems to be working, although shouldn't it be using EC_GROUP_order_bits() instead of hard-coding it for just a couple of curves? That's what I've submitted to the other engine,...