From: Tadeusz Struk <tadeusz.struk at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Policy check fails writing to NVRAM > 512B
Date: Wed, 13 Jun 2018 11:28:58 -0700 [thread overview]
Message-ID: <1ae2f36e-7bc1-6529-e532-c5b281f60da6@intel.com> (raw)
In-Reply-To: 231a0147-4fa9-71d7-587d-65efcf7af8c1@intel.com
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On 06/13/2018 11:13 AM, Tadeusz Struk wrote:
> On 06/13/2018 11:06 AM, Gabriela Limonta Márquez wrote:
>> $ export TSS2_LOG="all+ERROR,tcti+TRACE"
>>
>> $ tpm2_nvwrite -x 0x1800005 -a 0x1800005 -L sha256:0 -F pcr.value ta_config.cfg
>> ERROR: Failed to write NV area at index 0x1800005 (25165829) offset 0x200. Error:0x99d
>> ERROR: Unable to run tpm2_nvwrite
>>
>> Am I doing something wrong? or are the TSS logs available somewhere else after I execute the command and that is why I see nothing?
>>
>> I also tried enabling logging as TSS2_LOG="all+TRACE", but I only see debug and trace logs from marshal and none of them say error or anything similar.
>
> That all looks good. The only thing that's probably missing is that the debug is not compiled into TSS.
> It needs to be enabled at compile time by --with-maxloglevel=trace
> Please see ./configure --help
> Could you recompile TSS with that enabled and try again.
Just looked at the config and see that the 'trace' is the default if you build it from the repo.
Are you running your commands with sudo by any chance?
Thanks,
--
Tadeusz
next reply other threads:[~2018-06-13 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 18:28 Tadeusz Struk [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-13 18:31 [tpm2] Policy check fails writing to NVRAM > 512B
2018-06-13 18:13 Tadeusz Struk
2018-06-13 18:06
2018-06-13 17:47 Tadeusz Struk
2018-06-12 6:20
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ae2f36e-7bc1-6529-e532-c5b281f60da6@intel.com \
--to=tpm2@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox