tss2_createnv.1 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137
  1. .\" Automatically generated by Pandoc 1.19.2.4
  2. .\"
  3. .TH "tss2_createnv" "1" "APRIL 2019" "tpm2\-tools" "General Commands Manual"
  4. .hy
  5. .SH NAME
  6. .PP
  7. \f[B]tss2_createnv\f[](1) \-
  8. .SH SYNOPSIS
  9. .PP
  10. \f[B]tss2_createnv\f[] [\f[I]OPTIONS\f[]]
  11. .SH SEE ALSO
  12. .PP
  13. \f[B]fapi\-config(5)\f[] to adjust Fapi parameters like the used
  14. cryptographic profile and TCTI or directories for the Fapi metadata
  15. storages.
  16. .PP
  17. \f[B]fapi\-profile(5)\f[] to determine the cryptographic algorithms and
  18. parameters for all keys and operations of a specific TPM interaction
  19. like the name hash algorithm, the asymmetric signature algorithm, scheme
  20. and parameters and PCR bank selection.
  21. .SH DESCRIPTION
  22. .PP
  23. \f[B]tss2_createnv\f[](1) \- This command creates an NV index in the
  24. TPM.
  25. .SH OPTIONS
  26. .PP
  27. These are the available options:
  28. .IP \[bu] 2
  29. \f[B]\-p\f[], \f[B]\-\-path\f[]=\f[I]STRING\f[]:
  30. .RS 2
  31. .PP
  32. Path of the new NV space.
  33. .PP
  34. The path is composed of three elements, separated by "/".
  35. An nvPath starts with "/nv".
  36. The second path element identifies the NV handle range for the nv
  37. object.
  38. This includes the following values: Owner, TPM, Platform,
  39. Endorsement_Certificate, Platform_Certificate, Component_OEM, TPM_OEM,
  40. Platform_OEM, PC\-Client, Server, Virtualized_Platform, MPWG, Embedded.
  41. The third path element identifies the actual NV\-Index using a
  42. meaningful name.
  43. .RE
  44. .IP \[bu] 2
  45. \f[B]\-t\f[], \f[B]\-\-type\f[]=\f[I]STRING\f[]:
  46. .RS 2
  47. .PP
  48. Identifies the intended usage.
  49. Optional parameter.
  50. Types may be any comma\-separated combination of:
  51. .IP
  52. .nf
  53. \f[C]
  54. \-\ "noda":\ Sets\ the\ noda\ attribute\ of\ a\ key\ or\ NV\ index.
  55. \-\ "bitfield":\ Sets\ the\ NV\ type\ to\ bitfield.
  56. \-\ "counter":\ Sets\ the\ NV\ type\ to\ counter.
  57. \-\ "pcr":\ Sets\ the\ NV\ type\ to\ pcr\-like\ behavior.
  58. \-\ Hint:\ If\ none\ of\ the\ previous\ three\ keywords\ is\ provided\ a\ regular\ NV
  59. \ \ index\ is\ created.
  60. \f[]
  61. .fi
  62. .RE
  63. .IP \[bu] 2
  64. \f[B]\-s\f[], \f[B]\-\-size\f[]=\f[I]INTEGER\f[]:
  65. .RS 2
  66. .PP
  67. The size in bytes of the NV index to be created.
  68. Can be omitted if size can be inferred from the type; e.g.
  69. an NV index of type counter has a size of 8 bytes.
  70. .RE
  71. .IP \[bu] 2
  72. \f[B]\-P\f[], \f[B]\-\-policyPath\f[]=\f[I]STRING\f[]:
  73. .RS 2
  74. .PP
  75. Identifies the policy to be associated with the new NV space.
  76. Optional parameter.
  77. If omitted then no policy will be associated with the key.
  78. .PP
  79. A policyPath is composed of two elements, separated by "/".
  80. A policyPath starts with "/policy".
  81. The second path element identifies the policy or policy template using a
  82. meaningful name.
  83. .RE
  84. .IP \[bu] 2
  85. \f[B]\-a\f[], \f[B]\-\-authValue\f[]=\f[I]STRING\f[]:
  86. .RS 2
  87. .PP
  88. The new UTF\-8 password.
  89. Optional parameter.
  90. If it is neglected then the user is queried interactively for a
  91. password.
  92. To set no password, this option should be used with the empty string
  93. ("").
  94. The maximum password size is determined by the digest size of the chosen
  95. name hash algorithm in the cryptographic profile (cf.,
  96. \f[B]fapi\-profile(5)\f[]).
  97. For example, choosing SHA256 as hash algorithm, allows passwords of a
  98. maximum size of 32 characters.
  99. .RE
  100. .SH COMMON OPTIONS
  101. .PP
  102. This collection of options are common to all tss2 programs and provide
  103. information that many users may expect.
  104. .IP \[bu] 2
  105. \f[B]\-h\f[], \f[B]\-\-help [man|no\-man]\f[]: Display the tools
  106. manpage.
  107. By default, it attempts to invoke the manpager for the tool, however, on
  108. failure will output a short tool summary.
  109. This is the same behavior if the "man" option argument is specified,
  110. however if explicit "man" is requested, the tool will provide errors
  111. from man on stderr.
  112. If the "no\-man" option if specified, or the manpager fails, the short
  113. options will be output to stdout.
  114. .RS 2
  115. .PP
  116. To successfully use the manpages feature requires the manpages to be
  117. installed or on \f[I]MANPATH\f[], See \f[B]man\f[](1) for more details.
  118. .RE
  119. .IP \[bu] 2
  120. \f[B]\-v\f[], \f[B]\-\-version\f[]: Display version information for this
  121. tool, supported tctis and exit.
  122. .SH EXAMPLE
  123. .IP
  124. .nf
  125. \f[C]
  126. tss2_createnv\ \-\-authValue=abc\ \-\-path=/nv/Owner/myNV\ \-\-size=20\ \-\-type="noDa"
  127. \f[]
  128. .fi
  129. .SH RETURNS
  130. .PP
  131. 0 on success or 1 on failure.
  132. .SH BUGS
  133. .PP
  134. Github Issues (https://github.com/tpm2-software/tpm2-tools/issues)
  135. .SH HELP
  136. .PP
  137. See the Mailing List (https://lists.01.org/mailman/listinfo/tpm2)