Map
Index
Random
Help
th

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

topics > all references > references i-l > QuoteRef: leroX1_1998 , p. 395



Topic:
security by secure domains
Group:
security
Topic:
weak vs. strong type checking
Topic:
data type by name or tags
Topic:
dynamic type checking
Topic:
type-safe and secure languages
Topic:
dynamic vs. static data type

Quotation Skeleton

types from the simply-typed .lambda.-calculus are too coarse … [enforcing a security policy] … filenames, and cryptographic keys … To this end, we introduce named types t … For instance, we could introduce a type filename, … The other unusual feature of a type system … validation of their argument. For each named type … For instance, PV(filename) could consist of all strings …   Google-1   Google-2

Copyright clearance needed for quotation.

Additional Titles

Quote: use named types for fine-grained types implemented by a program type; e.g., different kinds of strings
Quote: enforce type system with run-time validation checks on each argument; e.g., all file names belong to the /tmp directory

Related Topics up

Topic: security by secure domains (42 items)
Group: security   (23 topics, 802 quotes)
Topic: weak vs. strong type checking (39 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)

Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.