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

Question about Ext2FS and Data Encryption in Mystikos #1532

Open
StanPlatinum opened this issue Jan 22, 2025 · 1 comment
Open

Question about Ext2FS and Data Encryption in Mystikos #1532

StanPlatinum opened this issue Jan 22, 2025 · 1 comment

Comments

@StanPlatinum
Copy link

StanPlatinum commented Jan 22, 2025

Dear Mystikos team,

I was reviewing the documentation and noticed that ext2fs is mentioned as the protected filesystem, with integrity ensured by dm-verity. I have a few questions regarding this:

  • Does this imply that when using ext2fs, it is not possible to persist encrypted data from memory to disk?
  • If I want to persist data from memory to disk during runtime, does that mean hostfs is the only option?

It would be great if you could clarify how Mystikos handles the trade-off between integrity (via dm-verity) and encryption for disk persistence in these cases.

Thanks for your work on this project! Looking forward to your insights.

@ya0guang might also find this topic interesting.

@vtikoo
Copy link
Collaborator

vtikoo commented Jan 22, 2025

Yes ext2fs only supports ephemeral writes, i.e writes are lost when enclave terminates.
The threat model becomes more complicated with supporting persistent writes. For one the on-disk dm-verity roothash and Merkle tree would have to be updated.
ext2fs in Mystikos also comes in the dm-crypt flavor, where it might be easier to support persistent.
cc: @mikbras

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

2 participants