sealfile.1

来自「IBM开发的TPM的驱动, 有少量的例子可以供参考」· 1 代码 · 共 60 行

.\" Copyright 2004 IBM (Jeff Kravitz)
.\"
.\" Written Feb 24 2004, Jeff Kravitz
.\"
.TH sealfile 1  2004-04-15 "IBM" "TPM Utilities"
.SH NAME
sealfile \- seals a data file
.SH SYNOPSIS

sealfile [options] <key handle> <input file> <outputfile>

     
.SH DESCRIPTION
This command will seal a file.
Sealing a file means encrypting it with a storage key, and also
locking the encrypted data so that it cannot be decrypted
unless the PCR registers contain the values
they had when the file was sealed.
Currently, the values of PCR registers 0-6 are used.
The sealed file may also have a password, which must be specified when unsealing
the file.
.SH ARGUMENTS
.TP 5
key handle
is an 8-hex-digit number that specifies the TPM handle assigned to the
key that is to be used for sealing.
It is
usually obtained from the \fBloadkey\fP utility
when the key was loaded into the TPM.
.TP 5
input file
is the name of the file containing the data to be sealed.
The file to seal cannot be longer than the maximum block size which can be
encrypted by the specified RSA key. For RSA keys with a modulus 2048 bits
in length, this maximum is approximately 245 bytes.
Sealing is therefore usually used to encrypt
short items, such as other keys or passwords.
.TP 5
output file
This specifies the name of the output file, which contains the sealed data.
.SH OPTIONS
The following command line options are supported...
.TP 5                
-k <keypass>
specifies the key usage password,
which is any character string, up to 256 bytes long.
It specifies the password needed to use the key.
The actual "Authorization Data"
passed to the TPM is the 20 byte SHA1 hash of the user-specified password.
.TP 5                
-d <datapass>
which is any character string, up to 256 bytes long.
It specifies the password which will be required to unseal the file.
The actual "Authorization Data"
passed to the TPM is the 20 byte SHA1 hash of the user-specified password.
.SH "SEE ALSO"
loadkey(1), unsealfile(1)
.SH AUTHOR
Jeff Kravitz , IBM T. J. Watson Research Center