I think you are interpreting the spec correctly. Two things to try, in this order:
1 - Read the nvLocked bit in the permanent flags. If it's clear (which should never occur on a shipped production platform), the NV protections are still disabled. 2 - Run with the IBM SW TPM and look at or send me the trace. It should give us some good clues. On 5/12/2014 10:13 AM, Frank Grötzner wrote: > Hi, > > I'm wondering if I misunderstood the way the NVRAM permissions work > or if it's missing implementation... I thought by defining a NVRAM > area with AUTHREAD|AUTHWRITE or OWNERREAD|OWNERWRITE I would need the > supplied NVRAM or ownerpassword respectively to read and write to > that defined area. But during my tests it was possible to read and > write to it without any passwords: > ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ TrouSerS-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-users
