| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTinQf+psOnb_r38PdOzRMArcxOdKkQgO3g_3SCGS@mail.gmail.com> Date: Fri, 11 Mar 2011 18:32:26 +0530 From: shiraz hashim <shiraz.linux.kernel@...il.com> To: Santosh Shilimkar <santosh.shilimkar@...com> Cc: Russell King - ARM Linux <linux@....linux.org.uk>, sen wang <wangchendu@...il.com>, David Brown <davidb@...eaurora.org>, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org Subject: Re: questions about arm trustzone Hello Santosh, On Tue, Jan 25, 2011 at 5:16 PM, Santosh Shilimkar <santosh.shilimkar@...com> wrote: [...] > The code above won't give major details of how the monitor mode is > implemented. But as Russell said, it's pretty much vendor specific. > > On OMAP, We have standard API interfaces to enter into monitor > world. One of the parameter denotes the kind of service, is > requested. Sorry if following are very naive. What should be the attributes of a monitor implementation. - Should it be un-modifiable. - Does it run in normal (non-secure) mode ? - Who programs the monitor (and its vector addresses) ? - Would monitor intend to provide fixed services and how does it decides that the request for a particular service is valid enough to enter secure world ? - Are monitors debuggable ? thanks in advance for any kind help. -- regards Shiraz Hashim -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists