For logical AND you just extend the current policy hash by calling tpm2_policynv. So After calling tpm2_policypcr, just call tpm2_policynv with the NV index, and the operand, like eq for equal. See this for more details on the operands and operators: https://github.com/tpm2-software/tpm2-tools/blob/master/man/tpm2_policynv... Then to access the NV index, run the policy commands in the same order and pass the session like normal, as you do below via the 'tpm2_nvread -P "session:/tmp/session.ctx" ...' command. Is their another question I'm missing here, I usually am missing something obvious people ask :-p Another thing to consider, can you use tss2_ tools? They have a policy language that manages this all for you with a WYSIWIG policy builder: https://tpm2-software.github.io/fapipolicies/ > > > *** locking/sealing the nvindex > > > tpm2_pcrread $PCRS -o /tmp/pcr.bin > > tpm2_startauthsession -S /tmp/session.ctx tpm2_policypcr -S /tmp/session.ctx \ > -l $PCRS -f /tmp/pcr.bin -L /tmp/pcr.policy tpm2_policyauthorize -S > /tmp/session.ctx \ > -L /tmp/nvindex.policy -n signing_key.name tpm2_nvdefine -a > "ownerwrite|ownerread|policyread" \ > -P $PASSWD -L /tmp/nvindex.policy $NVINDEX tpm2_flushcontext > /tmp/session.ctx > > openssl dgst -sha256 --sign signing_key_private.pem \ > -out pcr.signature /tmp/pcr.policy > > echo "storedsecret" | tpm2_nvwrite -C o -P $PASSWD \ > -i- $NVINDEX > > > *** reading the nvindex using the signed policy > > > tpm2_loadexternal -C o -G rsa -u signing_key_public.pem \ > -c /tmp/key.ctx -n /tmp/key.name > > tpm2_startauthsession -S /tmp/session.ctx --policy-session tpm2_policypcr -S > /tmp/session.ctx \ > -l $PCRS -L /tmp/pcr.policy > tpm2_verifysignature -c /tmp/key.ctx \ > -f rsassa -g sha256 \ > -m /tmp/pcr.policy -s pcr.signature -t /tmp/sigverify.tkt tpm2_policyauthorize -S > /tmp/session.ctx \ > -i /tmp/pcr.policy -n /tmp/key.name -t /tmp/sigverify.tkt tpm2_nvread -P > "session:/tmp/session.ctx" -s 64 $NVINDEX tpm2_flushcontext /tmp/session.ctx > rm -f /tmp/sigverify.tkt > > > -- > paul moore > www.paul-moore.com > _______________________________________________ > tpm2 mailing list -- tpm2(a)lists.01.org > To unsubscribe send an email to tpm2-leave(a)lists.01.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

I think so. I think you can also drop the -L output until you end up with the policy you want. A policy is only a single hash, so every time you invoke a successful policy command, the little register in the TPM that keeps the current policy value gets extended. Then you capture that value with the -L output. Then you can use that when creating the object, so later when you need to use the object, that hash value has to match and all the steps must succeed, like checking PCR state, policy signed, etc. Because you're always extending the policy hash, it's a logical AND. The first thing when I saw policyOR was that I wanted policyAND and couldn't find it. Then Imran pointed this out to me. When you think about it, it's just like extending a PCR, you measure this and this and this ...