2014
DOI: 10.1007/978-3-319-14125-1_2
|View full text |Cite
|
Sign up to set email alerts
|

Information Flow in Object-Oriented Software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
6
1
1

Relationship

3
5

Authors

Journals

citations
Cited by 20 publications
(14 citation statements)
references
References 22 publications
0
14
0
Order By: Relevance
“…The entire specification and verification process took between two and three person weeks. We note that KeY is able to prove noninterference properties itself [21], [38], by using the technique of self composition [15]. (Though, again, we emphasize that proving (7) does not involve proving noninterference properties.)…”
Section: F Proving the Conservatism Property With Keymentioning
confidence: 94%
See 1 more Smart Citation
“…The entire specification and verification process took between two and three person weeks. We note that KeY is able to prove noninterference properties itself [21], [38], by using the technique of self composition [15]. (Though, again, we emphasize that proving (7) does not involve proving noninterference properties.)…”
Section: F Proving the Conservatism Property With Keymentioning
confidence: 94%
“…1 This is sufficient for applications concerned with cryptographic security properties (see Theorem 3). More general definitions of non-interference can for example be found in [38].…”
Section: Preliminariesmentioning
confidence: 99%
“…In particular, we build upon work presented in [16,12], where symbolic execution is used as a means to generate test cases for functional properties. Logic-based approaches such as [7,23] are fully precise and at the same time can flexibly express various information flow properties beyond the policies presented in this paper. The verification process is not fully automatic, however, and non-trivial interactions with the theorem prover are required.…”
Section: Related Workmentioning
confidence: 99%
“…3 Overflow checking can be disabled to treat integers as mathematical integers. 4 As usual, modulo bugs in the implementation. Users launch AutoProof on the current project, or on specific classes or members thereof.…”
Section: User Interface (Ui)mentioning
confidence: 99%
“…A command whose execution may modify objects in set declares its frame specification using a clause modify (set). Since Eiffel doesn't natively support modify clauses, AutoProof introduces a dummy feature named modify, which can be used in a routine's precondition to specify the frame, as it is done in various places in 4 The observer pattern in AutoProof using semantic collaborations. See [42] for a detailed explanation to specify that pushing an element onto the stack modifies the model attribute sequence of the Current instance (denotes by this in other languages); this stipulates that it may modify Current.list, but it should not modify any model attribute other than Current.sequence.…”
Section: Framingmentioning
confidence: 99%