Re:UC Berkeley to build open-source secure enclave using RISC-V
by wyldfire on Thursday December 13, 2018 @11:21PM
(#18678447)
Tagged memory is the biggest game changer for security IMO. RISC-V has a proposal IIRC, but ARM has a product (ARMv8.5) that looks like it will really raise the bar.
[ Parent
| on HN ]
Re:UC Berkeley to build open-source secure enclave using RISC-V
by anonymousDan on Friday December 14, 2018 @06:32AM
(#18680109)
Can you point me to some resources on this?
Re:UC Berkeley to build open-source secure enclave using RISC-V
by wyldfire on Friday December 14, 2018 @06:51AM
(#18680194)
ARM: https://community.arm.com/processors/b/blog/posts/arm-a-prof...
RISC-V: https://www.lowrisc.org/docs/tagged-memory-v0.1/tags/
You can think of this feature like a hardware ASan. Instead of using ASan as a design tool, you could use it as a security feature.
Capitalizing on this feature requires compiler and C lib changes. I'd bet that the support should be available in popular open source compilers before ARM ships.
Re:UC Berkeley to build open-source secure enclave using RISC-V
by anonymousDan on Friday December 14, 2018 @07:37AM
(#18680371)
Thanks, they look pretty interesting. Do you know what granularity the ARM tagging supports (e.g. byte level)? Would be interesting to see performance numbers - although I guess the hw is not available yet?
Re:UC Berkeley to build open-source secure enclave using RISC-V
by wyldfire on Friday December 14, 2018 @09:16AM
(#18680923)
IIRC the ARM tagging would protect ~8 (maybe 16?) byte regions. More info on this is at [1] [2] -- note that some of this discusses a software-only approach (with likely higher performance impact).
I think the majority of performance cost for HW Asan will come from the additional bits stored to memory, but it was "modest" (< 5%?). A couple of additional CPU instructions during memory allocate and free, these are probably of negligible impact.
[1] https://arxiv.org/abs/1802.09517
[2] https://clang.llvm.org/docs/HardwareAssistedAddressSanitizer...