Timeline for Employ fscrypt to securely protect, from data-at-rest exposure, all files+data installed after an initial Linux system build?
Current License: CC BY-SA 4.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2022 at 21:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 2, 2022 at 21:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 31, 2022 at 20:44 | answer | added | Johnny Utahh | timeline score: 1 | |
| Mar 28, 2020 at 2:30 | comment | added | Johnny Utahh | An additional LUKS-in-a-file account is here, employing a "sparse + expanding" file behavior. Seems to be another example of just what we were seeking (making a LUKS filesystem in a VM without having to "partition" underlying VM filesystem/storage). | |
| Mar 27, 2020 at 21:53 | comment | added | Johnny Utahh | We just discovered encrypted loop-device (basically "mount a filesystem within a file combined with some sort of LUKS or other encryption") support in at least Ubuntu (I just tested it, it seems to work). This is a "eureka!" moment for my team. I'm wondering why no one mention it before? Or if they did, we were not paying attention, and for that we apologize. | |
| Oct 14, 2019 at 16:23 | comment | added | Johnny Utahh | The encrypted-volume-docker (inside the VPS) idea is growing on me. Maybe using something like: github.com/containers/docker-lvm-plugin | |
| Oct 5, 2019 at 18:26 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 18 characters in body
|
| Oct 5, 2019 at 18:16 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 200 characters in body
|
| Oct 5, 2019 at 18:11 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 200 characters in body
|
| Oct 5, 2019 at 18:03 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
deleted 1 character in body
|
| Oct 5, 2019 at 17:59 | comment | added | Johnny Utahh | [continuing from above...] We can (maybe) realize this at the cost of spend more money and effort to build out, effectively, virtual machines (containers) on top of virtual machines (VPSes). Or at this point, we rent or co-locate dedicated hardware instead of VPSes - although that dramatically limits our operational (re-deployment, etc) flexibility. Thoughts on this idea, and any others, very welcome. | |
| Oct 5, 2019 at 17:54 | comment | added | Johnny Utahh | Latest idea: employing custom-built, with ext4 rootfs encrypted at time of OS install, Linux containers (like docker or others, en.wikipedia.org/wiki/List_of_Linux_containers) to work around the hosting-providers limitations. Some container-based rig-up might have a chance to accomplish this goal and all the associated benefits. [continued...] | |
| Oct 5, 2019 at 15:38 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
deleted 11 characters in body
|
| Oct 4, 2019 at 23:06 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
outlining 3 different potential benefits
|
| Oct 4, 2019 at 23:01 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
outlining 3 different potential benefits
|
| Oct 4, 2019 at 22:47 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
outlining 3 different potential benefits
|
| Oct 4, 2019 at 22:36 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
outlining 3 different potential benefits
|
| Oct 4, 2019 at 22:26 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
outlining 3 different potential benefits
|
| Oct 4, 2019 at 16:21 | comment | added | Johnny Utahh | fyi. I also just now created a DigitalOcean community query (pointing to this question): digitalocean.com/community/questions/… | |
| Oct 4, 2019 at 15:12 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 289 characters in body
|
| Oct 4, 2019 at 14:44 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 618 characters in body
|
| Oct 4, 2019 at 14:39 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 618 characters in body
|
| Oct 4, 2019 at 14:32 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 618 characters in body
|
| Oct 4, 2019 at 14:10 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
Adding eCryptfs reference
|
| Oct 4, 2019 at 13:54 | comment | added | Johnny Utahh | fyi. I posted this same question to an fscrypt github.com issue: github.com/google/fscrypt/issues/155 | |
| Oct 4, 2019 at 13:48 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 75 characters in body
|
| Oct 4, 2019 at 13:42 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 69 characters in body
|
| Oct 4, 2019 at 13:35 | history | edited | Johnny Utahh | CC BY-SA 4.0 |
added 43 characters in body
|
| Oct 4, 2019 at 13:29 | history | asked | Johnny Utahh | CC BY-SA 4.0 |