* TmpFs Incorporation Of FsCrypt?
@ 2026-01-14 7:03 Nathan Royce
0 siblings, 0 replies; 2+ messages in thread
From: Nathan Royce @ 2026-01-14 7:03 UTC (permalink / raw)
To: LKML; +Cc: linux-mm, Andrew Morton, Hugh Dickins
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
I recently saw the PRs for BTRFS relating to FSCRYPT, and thought I'd
explore the fscrypt package.
I started with `status` before moving to `setup` on the `/tmp` path which
is tmpfs.
As expected I'm sure, I got: `[ERROR] fscrypt setup: filesystem type tmpfs
is not supported for fscrypt setup`
Looking in https://github.com/google/fscrypt, I saw:
https://github.com/google/fscrypt/blob/ea916da7fa9844cc3da608e75510f478c7b09f7d/cli-tests/t_not_supported.sh
which coincides with my presumably expected error.
But I also saw: `The source files are located on an in-memory filesystem
such as tmpfs.` in the main README, which makes me wonder if there is
intent/plan to bring fscrypt to tmpfs.
I'm kind of thinking a use case of having keys and/or a password manager
database on external/encrypted storage, that gets transferred to some
random path in `/run/user/<#>` (tmpfs) on login where it is encrypted as
well (then the storage is unmounted/locked/removed), and the respective
program that uses the file(s) would point to a freshly generated config
that points to the random location.
[-- Attachment #2: Type: text/html, Size: 1408 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* TmpFs Incorporation Of FsCrypt?
@ 2026-01-14 7:25 Nathan Royce
0 siblings, 0 replies; 2+ messages in thread
From: Nathan Royce @ 2026-01-14 7:25 UTC (permalink / raw)
To: LKML; +Cc: linux-mm, Andrew Morton, Hugh Dickins
I recently saw the PRs for BTRFS relating to FSCRYPT, and thought I'd
explore the fscrypt package.
I started with `status` before moving to `setup` on the `/tmp` path
which is tmpfs.
As expected I'm sure, I got: `[ERROR] fscrypt setup: filesystem type
tmpfs is not supported for fscrypt setup`
Looking in https://github.com/google/fscrypt, I saw:
https://github.com/google/fscrypt/blob/ea916da7fa9844cc3da608e75510f478c7b09f7d/cli-tests/t_not_supported.sh
which coincides with my presumably expected error.
But I also saw: `The source files are located on an in-memory
filesystem such as tmpfs.` in the main README, which makes me wonder
if there is intent/plan to bring fscrypt to tmpfs.
I'm kind of thinking a use case of having keys and/or a password
manager database on external/encrypted storage, that gets transferred
to some random path in `/run/user/<#>` (tmpfs) on login where it is
encrypted as well (then the storage is unmounted/locked/removed), and
the respective program that uses the file(s) would point to a freshly
generated config that points to the random location.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-01-14 7:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-01-14 7:03 TmpFs Incorporation Of FsCrypt? Nathan Royce
2026-01-14 7:25 Nathan Royce
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox