128-Bit Addressing in RISC-V and Security

More documents

Recommendations

Info

Shadow Stack • Independent, somewhat of address proposal • Solves classical virus/malware agacks – Heap Overflow • Change return address – WriCng over Stack – Heap Fung Hui Agacks [8] • Hardware protected SP, AP, FP – Akin to domain crossing – Return via shadow stack 2016 _NOV _RISCV_WORKSHOP 40
Shadow Stack - Architecture Return Block Return Block FP AP FP AP Stack Pointer Stack Pointer Shadow Stack (Hardware Maintained) User Visible Stack Different Domain, Same virtual address Can not write/read Shadow Stack Return via THIS STACK 2016 _NOV _RISCV_WORKSHOP 41
Page 1 and 2: 128-Bit Addressing in RISC-V and Se
Page 3 and 4: Background • Since the late 70’
Page 5 and 6: What Happened • MulCcs at MIT - U
Page 7 and 8: Going Forward • There Time is to
Page 9 and 10: ProtecCon ObjecCves • The origina
Page 11 and 12: Previous Efforts • Another soluCo
Page 13 and 14: Strawman - RV128I OBJECT ID Byte Of
Page 15 and 16: What is a Object ? • A Object is
Page 17 and 18: AuthenCcaCon • The address space
Page 19 and 20: Memory Management • Each object c
Page 21 and 22: 64 BIT LINUX -Memory Management Pro
Page 23 and 24: Exascale Issues • Subject to cost
Page 25 and 26: 128- BIT VIRTUAL ADDRESSING -Protec
Page 27 and 28: ACL (Access Control List) - ENTRY P
Page 29 and 30: REFERENCE MONITOR • It must valid
Page 31 and 32: Summary • Compare to CHERI [12] -
Page 33 and 34: References • [12] Robert N.M. Wat
Page 35 and 36: RevocaCon • Every client has a
Page 37 and 38: Some Object UID Math • 60 seconds
Page 39: ProtecCon in Unified Name Space •

128-Bit Addressing in RISC-V and Security

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?