Frieder Erdmann

@prp Could you comment on this? The company I'm working for has significant interest in multi party attestation and would invest resources to provide a pull request for this feature....

@brenzi @m1ghtym0 No PR is in work at this moment. For Integritee the priority is #293. Only after this a valid signature for the update log will be useful.

@thomasten Is there an ETA yet for data sealing for `hostfs` without modifying the application code ?

@brenzi @mullefel @daniel-weisse Only mrenclave updates are required for Integritees use case. However it is likely that in some situations secrets should be passed on to the new enclave version,...

@m1ghtym0 Let's try to use an example to see whether that fits our use case. There's a gramine application that uses a marblerun provided secret to encrypt its state as...

@m1ghtym0 Integritee is still working on the "Attesteer" project which brought up this issue. However priority is concentrated else where currently. @niederb will continue work on the Attesteer and will...

Defining allowed, trusted and protected files via mount points solves #359 so I am closing it. For naming I would like to throw in: `unprotected`, `integrity_protected` and `confidentiality_protected` Another question...

@dimakuv @mkow @woju thanks for your detailed answers. I am 99% sure that the signed Gramine binaries are sufficient for our use case for now. However this is likely to...

We've run into this problem graminizing `geth`. As this issue has seen some activity recently, I am wondering if a patch is already being developed now or in the near...

@dimakuv Great news! Please let us know once there is a final decision on whether a flock implementation will be included in v1.4 or not.