Re: [apache/incubator-teaclave-sgx-sdk] The reason for TCSPolicy requirement on env_logger? (#271)

2020-10-08 Thread Adam Szkoda
Awesome, thank you! I did some tests and it's almost perfect. One glitch that I found is that within Rust tests, the `--nocapture` flag isn't being respected. What I mean by that is when I initialize the logger like so (note the `is_test(true)` call) : ```Rust #[no_mangle] pub extern

Re: [apache/incubator-teaclave-sgx-sdk] The reason for TCSPolicy requirement on env_logger? (#271)

2020-10-06 Thread Yu Ding
Hi @adaszko , Long story short: i just solved it in https://github.com/mesalock-linux/env_logger-sgx/commit/ae2a39b53827b0ca074a2966a554ba1a998d7836 . To get rid of the TCSPolicy limitation, use this line in your enclave's Cargo.toml ```toml env_logger = { git = "https://github.com/mesalock-lin

[apache/incubator-teaclave-sgx-sdk] The reason for TCSPolicy requirement on env_logger? (#271)

2020-10-05 Thread Adam Szkoda
Hi! I was trying to use the logging library within an enclave as described at https://github.com/apache/incubator-teaclave-sgx-sdk/tree/master/samplecode/logger#usage and came across the `TCSPolicy = 0` requirement. Everything works great with that setting. The problem is, unfortunately, I ha