Dmitrii Kuvaiskii
Dmitrii Kuvaiskii
> Wasn't GSC supposed to follow current `master`, or maybe we've changed this policy and I forgot? No, why. GSC can use any compatible version. I think the policy is...
Create a GSC PR too: https://github.com/gramineproject/gsc/pull/62
@mythi If you want to test it, then you need to do like this, all in the GSC repo: 1. Checkout the branch corresponding to PR #62: ``` git checkout...
@nmwael Have you tried adding: ``` fs.mounts = [ { uri = "file:/usr/share/dotnet", path = "/gramine/app_files" }, ] ``` to your GSC manifest file? See our discussions above.
> I would expect that the contents of the directory (/usr/share/dotnet) was mounted in /gramine/app_files not replacing it? Oh, you are right, the contents get **replaced** when you mount the...
Let me close this issue, since the author is inactive.
Jenkins, test this please
Reviving this 6-months-old thread. We hit this problem again, and need to solve it sooner than later. Let me summarize the problem: - Encrypted (aka Protected) Files in Gramine use...
> But if the application is not specifically modified for Gramine, it may refuse to run if the file is r/o. Then the data will be lost if it is...
Looking at this thread again, my current idea is this: - Keep a single on-startup MRENCLAVE/MRSIGNER sealing key (do **not** introduce per-file keys). - On Gramine startup: - if Gramine...