Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kolide check failing to detect FDE when ecryptfs is stacked on top #1964

Open
smlx opened this issue Nov 20, 2024 · 0 comments
Open

Kolide check failing to detect FDE when ecryptfs is stacked on top #1964

smlx opened this issue Nov 20, 2024 · 0 comments

Comments

@smlx
Copy link

smlx commented Nov 20, 2024

We have a Linux user with FDE:

user@host:~$ lsblk
NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
nvme0n1             259:0    0 953.9G  0 disk
├─nvme0n1p1         259:1    0   512M  0 part  /boot/efi
├─nvme0n1p2         259:2    0   1.7G  0 part  /boot
└─nvme0n1p3         259:3    0 951.7G  0 part
  └─nvme0n1p3_crypt 252:0    0 951.7G  0 crypt
    ├─vgmint-root   252:1    0 929.4G  0 lvm   /
    └─vgmint-swap_1 252:2    0   1.9G  0 lvm   [SWAP]

But the user is apparently stacking ecryptfs on top of the FDE for their home directory and this is tripping up Kolide which is incorrectly reporting that the user's home directory is not encrypted:

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant