Searched refs:crypt (Results 1 – 10 of 10) sorted by relevance
62 bool crypt : 1; member91 return fs_mgr_flags.crypt || fs_mgr_flags.force_crypt || fs_mgr_flags.force_fde_or_fbe; in is_encryptable()
564 saInfo.crypt = XfrmAlgo{ in ipSecAddSecurityAssociation()880 nlattr_algo_crypt crypt{}; in updateSecurityAssociation() local912 {&crypt, 0}, // adjust size if crypt algo is present in updateSecurityAssociation()928 if (!record.aead.name.empty() && (!record.auth.name.empty() || !record.crypt.name.empty())) { in updateSecurityAssociation()935 record.crypt.key.size() > MAX_KEY_LENGTH) { in updateSecurityAssociation()952 len = iov[CRYPT].iov_len = fillNlAttrXfrmAlgoEnc(record.crypt, &crypt); in updateSecurityAssociation()983 strncpy(algo->crypt.alg_name, inAlgo.name.c_str(), sizeof(algo->crypt.alg_name)); in fillNlAttrXfrmAlgoEnc()984 algo->crypt.alg_key_len = inAlgo.key.size() * 8; // bits in fillNlAttrXfrmAlgoEnc()
123 XfrmAlgo crypt; member278 xfrm_algo crypt; member
402 netdutils::extract(buf, encryptAlgo.crypt); in testIpSecAddSecurityAssociation()
287 lhs.crypt == rhs.crypt && in CompareFlags()437 flags.crypt = true; in TEST()485 flags.crypt = true; in TEST()
42 `dm-crypt` or `dm-default-key` device. This means the underlying device is
188 entry->fs_mgr_flags.crypt = true; in ParseFsMgrFlags()
959 if (entry.fs_mgr_flags.crypt) { in needs_block_encryption()
550 ### dm-crypt for integrity561 dm-crypt. Although this provides some level of protection against tampering, its
516 (entry.fs_mgr_flags.crypt || entry.fs_mgr_flags.force_crypt || in get_crypt_info()