Lines Matching +full:quality +full:- +full:of +full:- +full:service

6 key ring service.  Both of these new types are variable length symmetric keys,
9 of a Trusted Platform Module (TPM) chip for greater security, while Encrypted
22 -------
26 trouser's utility: "tpm_takeownership -u -z".
29 -------
36   #> tsscreateprimary -hi o -st
38   #> tssevictcontrol -hi o -ho 80000000 -hp 81000001
42   #> tpm2_createprimary --hierarchy o -G rsa2048 -c key.ctxt
44   #> tpm2_evictcontrol -c key.ctxt 0x81000001
55        keyhandle=    ascii hex value of sealing key
62        pcrinfo=	     ascii hex of PCR_INFO or PCR_INFO_LONG (no default)
68                      are sha1, sha256, sha384, sha512 and sm3-256.
76 "keyctl print" returns an ascii hex copy of the sealed key, which is in standard
78 Trusted Keys can be 32 - 128 bytes (256 - 1024 bits), the upper limit is to fit
84 'master' key can either be a trusted-key or user-key type.  The main
85 disadvantage of encrypted keys is that if they are not rooted in a trusted key,
90 The decrypted portion of encrypted keys can contain either a simple symmetric
91 key or a more complex structure. The format of the more complex structure is
96     keyctl add encrypted name "new [format] key-type:master-key-name keylen"
99     keyctl update keyid "update key-type:master-key-name"
104 	key-type:= 'trusted' | 'user'
107 Examples of trusted and encrypted key usage:
109 Create and save a trusted key named "kmk" of length 32 bytes.
122            -3 --alswrv    500   500  keyring: _ses
123      97833714 --alswrv    500    -1   \_ keyring: _uid.500
124     440502848 --alswrv    500   500       \_ trusted: kmk
167 The initial consumer of trusted keys is EVM, which at boot time needs a high
168 quality symmetric key for HMAC protection of file metadata.  The use of a
208 with payload size of 32 bytes. This will initially be used for nvdimm security