128-Bit Addressing in RISC-V and Security

More documents

Recommendations

Info

Example using An ApplicaCon Steve Wallach – OBJECT Adobe PDF Reader - OBJECT • Can Execute in My Domain – Can read and write my file system • Can execute in different domain – Determine level of trust – Can read my data, but not write – Can’t send data back to ADOBE (network permissions) • Adobe FLASH - NO ACCESS 2016 _NOV _RISCV_WORKSHOP 18
Memory Management • Each object can have its OWN memory management structure – Page Tables – Hashed Indices – PGAS like • There is NO ACCESS bits associated with the management of storage (e.g., read, write, execute, etc..) – Management is separate from protecRon • Each object can choose to have object size for constraint access checking (bounds check). 2016 _NOV _RISCV_WORKSHOP 19
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: AuthenCcaCon • The address space
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 and 40: ProtecCon in Unified Name Space •
Page 41: Shadow Stack - Architecture Return

128-Bit Addressing in RISC-V and Security

Create successful ePaper yourself

Delete template?

Save as template?