[cap-talk] Security by safe language processing

Ben Kloosterman bklooste at gmail.com
Sun Sep 6 22:55:00 PDT 2009


Sorry I didn't see the above before firing off my last message.

I think I understand the above approach.  Do you agree that such an
approach is very different from current systems in that with it
one can't move binaries from system to system?

 

It is different from traditional Unix  but is common with Java and  CLR apps
. It is actually an advantage as the "Assemblies" are normally signed by the
developer . Note you can still copy the Assembly from machine to machine
knowing it  has not been tampered with due to signing..


It seems to me that a cache invalidating event could have serious
consequences for system performance - at least for a time.



Only a little bit more than starting the equivalent Java apps which normally
compiles it every time you start  , the checking is not that heavy  It is an
argument however in Language based systems  whether to go eg 

 

Install time , strongly optimized , fully inlined ( including the kernel)  ,
thoroughly checked vs  Run Time Jit with lesser optimizations and checking. 

 

Regards, 


Ben

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/cap-talk/attachments/20090907/f830b847/attachment.html 


More information about the cap-talk mailing list