Christoph M. Wintersteiger
Christoph M. Wintersteiger
There are other constraints than just sortedness and I don't think we should pull in an external library for the enclave side of this. On the host side it might...
My work is mostly between OE and LKL, i.e. before LKL starts up. Can I use all of OE's musl at those points in the code or just the *alloc...
@prp basically, yes. I started with putting the entire configuration into the json configs, I think there will be very few settings that we don't want attested, so I don't...
Yes, I think we should have a single struct that corresponds to the json config, otherwise it will be very tricky for users/reviewers to see what is in fact attested...
These are used in the new json parser without an `oe_*` version: `strcpy`, `strtoll`, `strtod`, `strtoull`. Would it simplify things if we built `src/enclave` without sgxlkl-musl and only with oe-musl?
(Just in case you haven't come across it before: thread locals may be reinitialized upon ecalls. For some reason this was the default behavior when I last looked at it,...
A whole core just for the ticker? That seems a bit excessive. Time is always tricky. Any enclave code basically has to assume that it can't rely on any timing...
See also #576
That definition is in mbedTLS and there are lots of copies of `#define mbedtls_calloc calloc` all over their codebase. (Yes, OE's mbedTLS, but that makes no difference here.) Most of...
Yeah, I think that's a viable solution, digging deeper.