Replies: 1 comment 7 replies
-
This means that you have your file on the host under the root directory (
You can't have "some file" on the host filesystem and use it as "Gramine encrypted file". Gramine uses a special format for encrypted files, which has a special header and metadata, in addition to the actual encrypted contents of the file. Thus, the file must not exist on the host filesystem -- it must be created by Gramine. Of course, after the file was created by Gramine, it can be read again by Gramine (e.g., after you restart the Gramine app). |
Beta Was this translation helpful? Give feedback.
-
|
Sure:
|
Beta Was this translation helpful? Give feedback.
-
|
This part of log doesn't show the root cause. Please copy the part of the log before it. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry my bad:
What caught my eye is:
Which I guess is because I'm testing with gramine-direct, do you think it might be the cause here? |
Beta Was this translation helpful? Give feedback.
-
Yes, this is the problem. If you just want to test/debug with gramine/CI-Examples/sqlite/manifest.template Lines 20 to 27 in 72f6524 |
Beta Was this translation helpful? Give feedback.
-
|
@dimakuv it is been so helpful thank you so much! |
Beta Was this translation helpful? Give feedback.
-
Hello!
I am trying to write to append a sealed file and I think I'm doing it wrong. Currently I have an empty file on the filesystem and trying to append and seal it using the mrenclave. Have the following line in my manifest:
{ type = "encrypted", path = "/try.csv", uri = "file:/try.csv", key_name = "_sgx_mrenclave" },When I trying to write the file I receive access denied (I guess the file is readonly).
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions