Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ambiguity in ACL Documentation #483

Open
fangyi-zhou opened this issue Aug 11, 2017 · 4 comments
Open

Ambiguity in ACL Documentation #483

fangyi-zhou opened this issue Aug 11, 2017 · 4 comments
Labels

Comments

@fangyi-zhou
Copy link

fangyi-zhou commented Aug 11, 2017

In https://github.com/ARMmbed/uvisor/blob/master/docs/lib/API.md
acl_list is List of ACLs for the module

However, the the parameter is supposed to be ACLs for peripherals/IRQs

@fangyi-zhou fangyi-zhou changed the title Ambiguity in ACL Ambiguity in ACL Documentation Aug 11, 2017
@fangyi-zhou
Copy link
Author

acl_list is accessed here

const UvisorBoxAclItem * region = box_cfgtbl->acl_list;

There is a check for whether the ACL is for IRQ, and assumes what is not IRQ is a peripheral. (Assumed from debug print)

DPRINTF(" - Peripheral: 0x%08X - 0x%08X (permissions: 0x%04X)\r\n",

@fangyi-zhou
Copy link
Author

fangyi-zhou commented Aug 11, 2017

Suggestion: Check whether UVISOR_TACL_PERIPHERAL is set and halt uVisor if check fails. Update the documentation accordingly.

@fangyi-zhou
Copy link
Author

Also: in the case that the design intent of the acl_list covering a larger range of ACL list than only IRQ and peripherals, there are other things that need to be considered:

  • Change the wording of debug message
  • Inspect vmpu_is_buffer_access_ok and verify the assumptions on ACL vMPU region correspondence

@ciarmcom
Copy link
Member

ARM Internal Ref: IOTSEC-415

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants