nothing terribly important but food for thought so in attempting to port to cortex-A8 i inevitably let my mind wonder to the question in what ways can we leverage the additional security extensions provided, "Trustzone"[1] || [2]
unfortunately it doesn't seem to be a natural fit for capability systems, by splitting things in to secure and insecure worlds, in some ways you could potentially avoid the need for attenuation, but you inevitably lose the ability to do fine grained access control the ability to give secure access to one device, yet withhold it from another while providing 'non-secure' access. though, it could maybe be used in combination with attenuation, it'd have to be in ways which neither compromise or tie us to this specific implementation. If nothing else, it can be used as possibly intended, transparently and on top of a system oblivious to it. I guess i'm curious if anyone else has any thoughts/knows of research done on the subject. googling doesn't really seem to provide anything but marketing stuff. http://infocenter.arm.com/help/topic/com.arm.doc.prd29-genc-009492c/index.html (pdf) http://infocenter.arm.com/help/topic/com.arm.doc.prd29-genc-009492c/PRD29-GENC-009492C_trustzone_security_whitepaper.pdf ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ CapROS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/capros-devel
