It does indeed look strange. On 2/12/2016 9:22 PM, Tadd Seiff wrote: > > The only way I can think to get good properties is to bypass most of the > stack and send the TPM_OwnerReadPubek command straight to TCSD.
That's what I'd do. Or you can experiment with the utilities that I ship with my software TPM, which bypass Trousers completely and go directly to /dev/tpm0. Or you could use trousers, but run them through the proxy that I ship with my SW TPM and examine the actual byte streams. Or you could run trousers in verbose mode and examine the byte streams. > Any other ideas or thoughts on why these values are wrong? No. Sorry. At the TPM level, there is no actual getpubek or ownerreadpubek command, so I can't even tell exactly what was running. It seems unlikely that there would be a bug in the TPM tools at this point. The ReadPubek command (probably what's running) is often disabled, so I thought you might be missing an error code and dumping garbage. However, if the public key is correct, that's unlikely. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ TrouSerS-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-users
