Enclave code in Go

[g2flyer]

Options

• GoTee: code (https://github.com/epfl-dcsl/gotee), paper ( https://www.usenix.org/conference/atc19/presentation/ghosn). No development since before paper got published. Also seems missing aspects like attestation or alike
• Graphene based: Status 2020-03-10: Michael talked with the graphene folks. There was an earlier fork (https://github.com/intel/GrapheneSGX-Golang-Support-and-Enhancement) but given the evolution and maturing of graphene that might not be a good starting point. "Mainstream" graphene is close to have golang support; what seems missing is the resolution of https://github.com/oscarlab/graphene/pull/1218. That said, there is probably not extensive testing and so some specific go modules could potentially still trigger graphene problems. Also note that with graphene you cannot do anymore ecall/ocalls, so all that would have to be done via some socket (e.g., via named pipe). So a project could be to write a modification to edger8 which given edl files creates the network-based equivalent of the current generated ocall/ecall code). Not sure though if that is something we would want to do under the umbrella of FPC ...
• other libos, e.g., SGX-LKL?
• ...

[mbrandenburger]

Adding ego to the list