| 
|
QuoteRef: hartPH12_2001
topics >
all references >
ThesaHelp:
references g-h
ThesaHelp:
ACM references f-l
Topic:
error safe systems
Topic:
safety critical systems
Topic:
embedded systems
Topic:
safe use of pointers
Topic:
security leaks and weaknesses
Topic:
type-safe and secure languages
Topic:
weak vs. strong type checking
Group:
security
Topic:
no need for efficiency
Reference
Hartel, P.H., Moreau, L., "Formalizing the safety of Java, the Java virtual Machine, and Java Card", ACM Computing Surveys, 33, 4, pp. 517-558, December 2001. Google
abstract ;;Quote: review of literature on formal models of Java safety; applications to smartcards; need better models
518 ;;Quote: Java guarantees memory and type safety at runtime and compile time; programs cannot forge pointers, overrun arrays, or apply an operator to the wrong type
518 ;;Quote: a secure program accesses resources as defined by an audited, security policy; including execution time
ThesaHelp: references g-h (299 items)
ThesaHelp: ACM references f-l (241 items)
Topic: error safe systems (75 items)
Topic: safety critical systems (32 items)
Topic: embedded systems (26 items)
Topic: safe use of pointers (102 items)
Topic: security leaks and weaknesses (56 items)
Topic: type-safe and secure languages (42 items)
Topic: weak vs. strong type checking (39 items)
Group: security (23 topics, 802 quotes)
Topic: no need for efficiency (28 items)