ThesaHelp: references i-l
ThesaHelp: ACM references f-l
Topic: weak vs. strong type checking
Topic: security by secure domains
Group: security
Topic: semantics by an abstract machine
Topic: data type by name or tags
Topic: dynamic type checking
Topic: type-safe and secure languages
Topic: dynamic vs. static data type
| |
Reference
Leroy, X., Rouaix, F.,
"Security properties of typed applets",
Conference record of POPL '98: the 25th ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages, San Diego, California, January 1998, ACM Press, pp. 391-403.
Google
Quotations
391 ;;Quote: strong typing protects the sandbox model by preventing arbitrary access to the computer running the execution environment
| 392 ;;Quote: specify a security policy in terms of sensitive store locations; i.e., locations or files which an applet must not modify
| 392 ;;Quote: use big-step operational semantics to monitor reachable locations under the security policy
| 395 ;;Quote: simple types are too coarse for a security policy; e.g., a string can be a message, a file name, or a cryptographic key
| 395+;;Quote: use named types for fine-grained types implemented by a program type; e.g., different kinds of strings
| 395+;;Quote: enforce type system with run-time validation checks on each argument; e.g., all file names belong to the /tmp directory
| 396 ;;Quote: guarantee sandbox security by well-typed applets and verified parameter references
|
Related Topics
ThesaHelp: references i-l (342 items)
ThesaHelp: ACM references f-l (241 items)
Topic: weak vs. strong type checking (39 items)
Topic: security by secure domains (42 items)
Group: security (23 topics, 802 quotes)
Topic: semantics by an abstract machine (38 items)
Topic: data type by name or tags (29 items)
Topic: dynamic type checking (43 items)
Topic: type-safe and secure languages (42 items)
Topic: dynamic vs. static data type (19 items)
|