ùISO8859-1¶YÐB*Gm=µ#óIBa+¤ Ð 0ð ! ? ^-}5«7á ‡ 5V ½ 2 07 c › ­ Ä; Ö`  s  ­ à Î!$ Ú"R ÿ# R$ r%! “&) µ'9 ß( ) 1* F+ ],4 y-9 ®. è/: þ091N2e3z4˜5i¸6R"7u8#•9%¹:0ß;9<J=\>s?"‹@ ®A(ÏB9øCR2D5…E»FÒGêHI'#J9KK…L!œMR¾N6O4HP}Q”R©SÄT`ÝU©>V€èW iXŠY¥Z¼[Ø\"õ][^t_1’`Äa%äb9 c$Ddie€fR góh i"j+;kglƒm  nÁoÚpòq$ rR/s)‚t9¬uævýwx³y#Óz!÷{9|S}j~!ŠR¬€Zÿ+Z‚B†ƒPÉ„:…U†t‡)‹ˆSµ‰R Š9\‹–Œ­#ÅŽ.é(-‘V’"t“1—”.É•1ø–/ *—2 Z˜“ ™©!!šS!Ë›"œ""?!"bž "„Ÿ*"¥ +"С+"ü¢,#(£-#U¤+#ƒ¥9#¯¦8#é§ $"¨$0©$Gª=$_«Á$¬%_­=%o®H%­¯5%ö°C&,±&p²&r³&´&¨µ&ƶ&ÛCreates a revocable EK instead of the default non-revocable one. Requires [-g -o] or [-i]Name of the file containing the secret data used to revoke the EK.Generates a 20 byte secret that is used to revoke the EK. Requires [-o]Filename to write the secret data generated to revoke the EK.Error: could not open input file %sError: the secret data file %s contains less than %d bytes. Aborting ... WARNING: Using only the first %d bytes of file %s for secret data Read %d bytes of secret data from file %s. Unable to open output file: %s Error: Unable to write %d bytes to the file %s. %d bytes written on file %s. Please specify an output file Please specify an output file The option -i, --infile is not valid with -g Please specify -i, --infile or -g, --generate-secret The option -o, --outfile is not valid with -i, --infileSee man pages for details. Creation of revocable EK succeeded, but writing the EK revoke authorization to disk failed. Printing the revoke authorization instead: You should record this data, as it's the authorization you'll need to revoke your EK! Unable to open the device. Error occured while writing the reset command: %d Error occured while reading the reset result: %d %d %s TPM not started. TPM Error occured: %d Reset successful Use TSS_WELL_KNOWN_SECRET as the operator's default secret.Use TSS UNICODE encoding for operator password to comply with applications using TSS popup boxesEnter operator password: Failed to get operator passwordDisplay current stateEnable TPMDisable TPMUse physical presence authorization.Use 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataChanging mode to check status. Changing mode to enable the TPM Changing mode to disable the TPM Changing mode to use force authorization Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Failed to get password Disabled status: %s Enter owner password: Unable to open the device. Error occured while writing the startup command: %d Error occured while reading the startup result: %d %d %s TPM already started. Error occured while reading the selftest result: %d %d %s Selftest successful TPM Error occured: %d Report current stateActivate TPM, requires rebootDeactivate TPM, requires rebootChange state immediately but only for this boot. Only valid in conjunction with the inactive parameter.Use 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataChanging mode to check status. Changing mode to activate the TPM. Changing mode to deactivate the TPM. Changing mode to temporarily deactivate the TPM Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Checking status: Enter owner password: Failed to get password Persistent Deactivated Status: %s Volatile Deactivated Status: %s Action requires a reboot to take effect Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Use 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataPublic PubEk access blocked, owner password required Enter owner password: Failed to get password Public Endorsement Key: Changing mode to check status. Changing mode to restrict PubEK access Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Display current statusRestrict PubEK read to owner onlyUse 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataSet the owner secret to all zeros (20 bytes of zeros).Set the SRK secret to all zeros (20 bytes of zeros).Enter owner password: Enter SRK password: Change the owner password.Change the SRK password.Use TSS UNICODE encoding for original password to comply with applications using TSS popup boxesChange password to a new one when current owner password is a secret of all zeros (20 bytes of zeros). It must be specified which password (owner, SRK or both) to changeChange password to a secret of all zeros (20 bytes of zeros). It must be specified which password (owner, SRK or both) to changeSRK "Enter new SRK password: "Enter new owner password: Enter owner password: Changing password for: %s. Failed to get new password. Change of %s password successful. Use TSS UNICODE encoding for new password to comply with applications using TSS popup boxesFailed to get owner password Changing mode to allow SRK access using SRK auth Changing mode to check status. Changing mode to restrist SRK access Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Allow SRK read access using SRK authDisplay current statusRestrict SRK read to owner onlyUse 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataEnter owner password: Failed to get password TPM 1.2 Version Info: Chip Version: %hhu.%hhu.%hhu.%hhu Spec Level: %hu Errata Revision: %hhu TPM Vendor ID: %c%c%c%c Vendor Specific data: TPM Version: Manufacturer Info: Use physical presence authorization.Use 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataChanging mode to use force authorization Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Enter owner password: Failed to get password TPM Successfuly Cleared. You need to reboot to complete this operation. After reboot the TPM will be in the default state: unowned, disabled and inactive. Changing mode to check status. Changing to prevent ownership mode Changing to allow ownership mode Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Display current statusAllow TPM takeownership commandPrevent TPM takeownership commandUse 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataPlease specify which file contains the secret to revoke the Ek (use option -i, --infile). Read %d bytes of secret data from file %s. WARNING: Using only the first %d bytes of file %s for secret data Error: the secret data file %s contains less than %d bytes. Aborting with %s... Filename containing the secret data used to revoke the EK.Unable to open input file: %s Report current status.Remove ability of the owner to clear TPM.Remove ability to clear TPM with physical presence. This action is not persistentUse 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization dataUsing TSS_WELL_KNOWN_SECRET to authorize the TPM command Enter owner password: Failed to get password Attempting to disable: %s ability. Report results of last test without retesting. TPM Test Results: Report current physical presence states.Assert that admin is present.Clear assertion of admin presence.Lock TPM presence assertion into specified state.Allow TPM to accept Physical Presence Command.Disallow TPM to accept Physical Presence Command.Allow TPM to accept Hardware Physical Presence.Disallow TPM to accept Hardware Physical Presence.Prevent further modification of TPM Physical Presence Command and Hardware Enablement states. THIS ACTION IS PERMANENT AND CAN NEVER BE UNDONE.Automatically respond yes to all prompts. Only use this if you are sure of the current state and don't want any extra checking done before setting the lifetime lockUse 20 bytes of zeros (TSS_WELL_KNOWN_SECRET) as the TPM secret authorization data.Changing mode to check status. Changing mode to assert presence. Changing mode to clear presence. Changing mode to lock presence. Changing mode to enable command presence. Changing mode to disable command presence. Changing mode to enable hardware presence. Changing mode to disable hardware presence. Changing mode to set lifetime presence lock. Changing mode to automatically answer yes. Using TSS_WELL_KNOWN_SECRET to authorize the TPM command Unable to determine current state without authorization TPM is owned Enter owner password: Failed to get password Unable to determine current state with the entered password. Unable to programatically determine the current setting of TPM Physcial Presence Command Enable and Hardware Enable states. Make sure you are aware of and comfortable with the current states. Current State: These will be the permanent values if you choose to proceed. This command cannot be undone. Are you sure you want to continue?[y/N] Setting the lifetime lock was confirmed. Continuing. Continuing to set the lifetime lock was declined. Action canceled. yChecking current status: Physical Presence Status: Requested to Change %s to %s Change to %s Failed Change to %s Successful