LCP_CRTPOLLIST(8) User Manuals LCP_CRTPOLLIST(8)NAME
lcp_crtpollist - create an Intel(R) TXT policy list
SYNOPSIS
lcp_crtpollist COMMAND [OPTION]
DESCRIPTION
lcp_crtpollist is used to create an Intel(R) TXT policy list.
OPTIONS --create
Create an TXT policy list. The following options are available:
--out file policy list file
[--ver version] version
[file]... policy element files
--sigh Sign an TXT policy list.
--pub key-file PEM file of public key
--out file policy list file
[--priv key-file] PEM file of private key
[--rev rev-ctr] revocation counter value
[--nosig] don't add SigBlock
--addsig
--sig file file containing signature (big-endian)
--out file policy list file
--show file
policy list file
--help Print out the help message.
--verbose
Enable verbose output; can be specified with any command.
EXAMPLES
Create policy list:
Assuming there have been two element file mle.elt and pconf.elt generated by lcp_crtpolelt(8) The following example can create an unsigned
policy list:
lcp_crtpollist --create --out list-unsig.lst mle.elt pconf.elt
Sign policy list:
Unsigned policy list can be signed by the command lcp_crtpollist(8) or openssl(1). The openssl(1) signing is supported for cases where the
signing environment is separate from the policy creation environment and the software allowed to run there is strictly controlled and
already supports openssl(1).
The following example uses openssl(1) to sign the list:
1 openssl rsa -pubout -in privkey.pem -out pubkey.pem
2 cp list-unsig.lst list-sig.lst
3 lcp_crtpollist --sigh --pub pubkey.pem --nosig --out list-sig.lst
4 openssl genrsa -out privkey.pem 2048
5 openssl dgst -sha1 -sign privkey.pem -out list.sig list-sig.lst
6 lcp_crtpollist --addsig --sig list.sig --out list-sig.lst
lcp_crtpollist can also be used to sigh a policy list. The following example are intended to be mutually exclusive with the preceding exam-
ple.
1 openssl genrsa -out privkey.pem 2048
2 openssl rsa -pubout -in privkey.pem -out pubkey.pem
3 cp list-unsig.lst list-sig.lst
4 lcp_crtpollist --sign --pub pubkey.pem --priv privkey.pem --out list-sig.lst
SEE ALSO lcp_crtpol2(8), lcp_crtpolelt(8), lcp_crtpollist(8), openssl(1).
tboot 2011-12-31 LCP_CRTPOLLIST(8)
Check Out this Related Man Page
RSAUTL(1SSL) OpenSSL RSAUTL(1SSL)NAME
rsautl - RSA utility
SYNOPSIS
openssl rsautl [-in file] [-out file] [-inkey file] [-pubin] [-certin] [-sign] [-verify] [-encrypt] [-decrypt] [-pkcs] [-ssl] [-raw]
[-hexdump] [-asn1parse]
DESCRIPTION
The rsautl command can be used to sign, verify, encrypt and decrypt data using the RSA algorithm.
COMMAND OPTIONS -in filename
This specifies the input filename to read data from or standard input if this option is not specified.
-out filename
specifies the output filename to write to or standard output by default.
-inkey file
the input key file, by default it should be an RSA private key.
-pubin
the input file is an RSA public key.
-certin
the input is a certificate containing an RSA public key.
-sign
sign the input data and output the signed result. This requires and RSA private key.
-verify
verify the input data and output the recovered data.
-encrypt
encrypt the input data using an RSA public key.
-decrypt
decrypt the input data using an RSA private key.
-pkcs, -oaep, -ssl, -raw
the padding to use: PKCS#1 v1.5 (the default), PKCS#1 OAEP, special padding used in SSL v2 backwards compatible handshakes, or no
padding, respectively. For signatures, only -pkcs and -raw can be used.
-hexdump
hex dump the output data.
-asn1parse
asn1parse the output data, this is useful when combined with the -verify option.
NOTES
rsautl because it uses the RSA algorithm directly can only be used to sign or verify small pieces of data.
EXAMPLES
Sign some data using a private key:
openssl rsautl -sign -in file -inkey key.pem -out sig
Recover the signed data
openssl rsautl -verify -in sig -inkey key.pem
Examine the raw signed data:
openssl rsautl -verify -in file -inkey key.pem -raw -hexdump
0000 - 00 01 ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ................
0010 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ................
0020 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ................
0030 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ................
0040 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ................
0050 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ................
0060 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ................
0070 - ff ff ff ff 00 68 65 6c-6c 6f 20 77 6f 72 6c 64 .....hello world
The PKCS#1 block formatting is evident from this. If this was done using encrypt and decrypt the block would have been of type 2 (the
second byte) and random padding data visible instead of the 0xff bytes.
It is possible to analyse the signature of certificates using this utility in conjunction with asn1parse. Consider the self signed example
in certs/pca-cert.pem . Running asn1parse as follows yields:
openssl asn1parse -in pca-cert.pem
0:d=0 hl=4 l= 742 cons: SEQUENCE
4:d=1 hl=4 l= 591 cons: SEQUENCE
8:d=2 hl=2 l= 3 cons: cont [ 0 ]
10:d=3 hl=2 l= 1 prim: INTEGER :02
13:d=2 hl=2 l= 1 prim: INTEGER :00
16:d=2 hl=2 l= 13 cons: SEQUENCE
18:d=3 hl=2 l= 9 prim: OBJECT :md5WithRSAEncryption
29:d=3 hl=2 l= 0 prim: NULL
31:d=2 hl=2 l= 92 cons: SEQUENCE
33:d=3 hl=2 l= 11 cons: SET
35:d=4 hl=2 l= 9 cons: SEQUENCE
37:d=5 hl=2 l= 3 prim: OBJECT :countryName
42:d=5 hl=2 l= 2 prim: PRINTABLESTRING :AU
....
599:d=1 hl=2 l= 13 cons: SEQUENCE
601:d=2 hl=2 l= 9 prim: OBJECT :md5WithRSAEncryption
612:d=2 hl=2 l= 0 prim: NULL
614:d=1 hl=3 l= 129 prim: BIT STRING
The final BIT STRING contains the actual signature. It can be extracted with:
openssl asn1parse -in pca-cert.pem -out sig -noout -strparse 614
The certificate public key can be extracted with:
openssl x509 -in test/testx509.pem -pubkey -noout >pubkey.pem
The signature can be analysed with:
openssl rsautl -in sig -verify -asn1parse -inkey pubkey.pem -pubin
0:d=0 hl=2 l= 32 cons: SEQUENCE
2:d=1 hl=2 l= 12 cons: SEQUENCE
4:d=2 hl=2 l= 8 prim: OBJECT :md5
14:d=2 hl=2 l= 0 prim: NULL
16:d=1 hl=2 l= 16 prim: OCTET STRING
0000 - f3 46 9e aa 1a 4a 73 c9-37 ea 93 00 48 25 08 b5 .F...Js.7...H%..
This is the parsed version of an ASN1 DigestInfo structure. It can be seen that the digest used was md5. The actual part of the certificate
that was signed can be extracted with:
openssl asn1parse -in pca-cert.pem -out tbs -noout -strparse 4
and its digest computed with:
openssl md5 -c tbs
MD5(tbs)= f3:46:9e:aa:1a:4a:73:c9:37:ea:93:00:48:25:08:b5
which it can be seen agrees with the recovered value above.
SEE ALSO dgst(1), rsa(1), genrsa(1)1.0.1e 2013-02-11 RSAUTL(1SSL)