Nigel Hathaway

Actually, instead of defining WIN32_LEAN_AND_MEAN, define NOCRYPT instead. In this way, you don't need to include winsock.h. See https://stackoverflow.com/questions/11040133/what-does-defining-win32-lean-and-mean-exclude-exactly

Actually, instread of defining WIN32_LEAN_AND_MEAN, define NOCRYPT instead. In this way, you don't need to include winsock.h. See https://stackoverflow.com/questions/11040133/what-does-defining-win32-lean-and-mean-exclude-exactly

It looks like we need to add the line: #include <winsock.h> after #include <windows.h> at line 52 of tssproperties.h

Thanks for this. Defining WIN32_LEAN_AND_MEAN solves this. However, new errors appear. In tssproperties.h, line 66 typedef SOCKET TSS_SOCKET_FD; fails as SOCKET is undefined. In tssproperties.c, TSS_CONTEXT claims to be undefined. Simarly in tsstransmit.c

Old eay libs referenced in Visual Studio project

Old eay libs referenced in Visual Studio project

Yes, I believe it does, and I think my question has been answered. I'll try it out and see...

Hmm.... I'm still not completely clear on how this is done and if it is possible. Firstly, the backup is a bit of a red herring. Let's leave that out. My (simplified down) scenario is this: I have a master key machine on which I create lots of keys to be re-assigned later. At a later date I decide I want to send one of the keys to a "user" machine, and we assume that the user has root access to that machine. What we need to be able to do is ensure that, having duplicated the key to that user machine,...