[GitHub] [mynewt-core] vrahane edited a comment on pull request #2716: util: Add sensitive data mynewt util to hide data in coredumps

[GitBox <gi...@apache.org>]

vrahane edited a comment on pull request #2716:
URL: https://github.com/apache/mynewt-core/pull/2716#issuecomment-963750769


   So, I think for protected variables on the stack, there are couple of options, others can comment more based on their experiences but I can think of the following:
   
   1. Best bet would be to define them in the `mynewt_protected` section
   2. Have a protected section per stack somehow, this would need to be done from the linker script with defining dummy sections per stack and updating `StackTop`, `StackLimit`, `ProtectedStackStart1` and `ProtectedStackEnd1` for example and when a trap comes in, clear the individual protected stack sections. Again, this would mean a lot of changes to the existing stuff, so not sure if that is the route we want to take here.
   3. A combined protected section for all stacks and clearing that section (Somewhat same as 1, but easily identifiable with a dedicated section)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@mynewt.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org