RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

echo foo | clevis encrypt tpm2 '{"pcr_ids": [0,1]}' succeeds, but it uses a different policy than what was requested, due to clevis failing to parse the PCR IDs correctly.
Further inspection shows that no PCR IDs were actually used: 

echo foo | clevis encrypt tpm2 '{"pcr_ids": [0,1]}' | jose jwe fmt -i- | jose fmt -j- -g protected -u- | tr -d '"' | jose b64 dec -i- | jose fmt -j- -Og clevis -Og tpm2 -Og pcr_ids -u-
<no output>
echo $?
7

If we pass a string instead of a JSON array, it works as expected:
echo foo | clevis encrypt tpm2 '{"pcr_ids": "0,1"}' | jose jwe fmt -i- | jose
fmt -j- -g protected -u- | tr -d '"' | jose b64 dec -i- | jose fmt -j- -Og clevis -Og tpm2 -Og pcr_
ids -u-
0,1
echo $?
0

Version-Release number of selected component (if applicable):
Tested with clevis-11-9.el8.x86_64

How reproducible: always


Steps to Reproduce:
1. echo foo | clevis encrypt tpm2 '{"pcr_ids": "0,1"}' | jose jwe fmt -i- | jose
fmt -j- -g protected -u- | tr -d '"' | jose b64 dec -i- | jose fmt -j- -Og clevis -Og tpm2 -Og pcr_
ids -u-

Actual results:
<no output>
echo $?
7

Expected results:
0,1
echo $?
0

Additional info:
Reported upstream at https://github.com/latchset/clevis/issues/103

AC: Upstream test suite covering special tpm2 usage will pass [1].

[1] https://github.com/latchset/clevis/blob/master/src/pins/tpm2/pin-tpm2

Let me fix a typo in the steps to reproduce, which should use the array:

1. echo foo | clevis encrypt tpm2 '{"pcr_ids": [0,1]}' | jose jwe fmt -i- | jose fmt -j- -g protected -u- | tr -d '"' | jose b64 dec -i- | jose fmt -j- -Og clevis -Og tpm2 -Og pcr_ids -u-

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (clevis bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4701