Lines Matching full:dsl
36 * All master keys are stored encrypted on disk in the form of the DSL
56 * The DSL Crypto Key Tree:
57 * The DSL Crypto Keys (DCK) are the in-memory representation of decrypted
60 * dataset will share a DSL Crypto Key, so they are also refcounted. Once the
65 * the DSL Crypto Keys can belong to multiple datasets, we maintain a tree of
67 * appropriate DSL Crypto Key. The management for creating and destroying these
224 * maintained through the DSL.
481 /* hold the dsl dir */
724 /* Release the wrapping key (the dsl key now has a reference to it) */
800 /* hold the dsl dir */
817 /* verify that the wkey is correct by opening its dsl key */
823 /* initialize the wkey encryption parameters from the DSL Crypto Key */
852 * be used to decrypt a DSL Crypto Key. We can simply cleanup and
940 /* hold the dsl dir */
1118 * DSL Crypto Keys for encryption. Callers must release the key with
1183 /* check if this dd has a has a dsl key */
1458 /* ignore special dsl dirs */
1468 * Stop recursing if this dsl dir didn't inherit from the root
1502 /* Recurse into all child dsl dirs. */
1513 * Recurse into all dsl dirs of clones. We utilize the skip parameter
1712 * the DSL Crypto Key to point to the target instead.
1765 * DSL Crypto Key and keylocation to reflect that. We also need to
1766 * update the DSL Crypto Keys of all children inheritting their
1967 /* Create or clone the DSL crypto key and activate the feature */
2180 * all of the fields of a DSL Crypto Key, as well as a fully specified
2277 /* lookup the values we need to create the DSL Crypto Key */
2293 /* if this is a new dataset setup the DSL Crypto Key. */
2295 /* zapify the dsl dir so we can add the key object to it */
2299 /* create the DSL Crypto Key on disk and activate the feature */
2395 * This function is used to sync an nvlist representing a DSL Crypto Key and
2442 /* lookup values from the DSL Crypto Key */
2491 * not correctly add these values to the wrapping key or the DSL
2578 /* create the DSL Crypto Key ZAP object */