Public bug reported: nvdefind tool takes the size MAX_NV_INDEX_SIZE(2048) as default, but got errors(0x2D5) returned on those platforms which don't have the size as default. https://github.com/tpm2-software/tpm2-tools/issues/2171
[Impact] Some machines which don't have enough MAX_NV_INDEX_SIZE as defaule will got "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area [Test cases] run nvdefine without specifying the size of data area [Solution] A fix patch has been committed and accepted by maintainer https://github.com/tpm2-software/tpm2-tools/commit/48594efa6f1faca50c73ce0d88f6e99eb0f5005c [Regression Potential] Minimal, it fixed the issue by checking the platform capabilities instead of using default. ** Affects: tpm2-tools (Ubuntu) Importance: Undecided Status: New ** Affects: tpm2-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tpm2-tools (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
