## Description
Fix build error when app depend teaclave_proto
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave/pull/347
-- Commit Summary --
* Fix rpc build error for app mode
-- File Changes --
M rpc/Cargo.toml (3)
M rpc
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-b
https://cacheoutattack.com/
With all these practical attacks in place for Intel (and AMD to a
different extent), what do you think the future of SGX and its
competitors will look like? Are there plans on supporting other
hardware enclaves that may be more secure (if they exist)?
--
Matt Sicker
## Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-b
>From what I understand, SGAxe is still utilizing TSX to leak data from LFB.
It's not a problem of SGX, but a problem of TSX. TSX breaks the security
guarantees provided by SGX, or VMX.
The TSX problem is not limited to attacking SGX, but also stealing memory
from Dom0 in Xen, or memory from the k
You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave-sgx-sdk/pull/247
-- Commit Summary --
* Add checks for untrusted memory allocation result.
-- File Changes --
M sgx_libc/src/linux/x86_64/ocall.rs (12)
-- Patch Links --
http
Merged #247 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/pull/247#event-3431670812
Hi Matt,
Thanks for bringing up this issue. Regardless of this specific attack
itself, let me answer another frequently asked question about
supporting other hardware enclaves.
Actually, we have investigated other hardware enclaves for a long
time. The following are commonly mentioned hardware TE
BTW, maybe we can write a blog about the implication of recent side
channel attacks in SGX. But we need some time to survey this problem
and collect enough materials.
On Wed, Jun 10, 2020 at 3:18 PM Mingshen Sun wrote:
>
> Hi Matt,
>
> Thanks for bringing up this issue. Regardless of this specifi
Merged #345 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/345#event-3431863069
Thanks for your help!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/345#issuecomment-642325363
Thanks for the explanations everyone! And a blog post sounds like a great idea.
On Wed, 10 Jun 2020 at 17:50, Mingshen Sun wrote:
>
> BTW, maybe we can write a blog about the implication of recent side
> channel attacks in SGX. But we need some time to survey this problem
> and collect enough mat
Merged #347 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/347#event-3431965537
#127 Description
Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context.
Fixes # (issue)
## Type of change (select or add applied and delete the others)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (no
Merged #350 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/350#event-3432057615
## Description
- Only allow info log for release build and triage log levels
Note that this feature can control a compile time filter
(https://docs.rs/log/0.4.8/log/#compile-time-filters).
Also, for log levels, I found that most `info!` are `debug!` and some are
`error!`. Please don't misuse
CI passed: https://ci.mesalock-linux.org/mssun/incubator-mesatee/927/
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/351#issuecomment-642389974
Merged #351 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/pull/351#event-3432407760
18 matches
Mail list logo
