Proceedings 10th Computer Security Foundations Workshop
DOI: 10.1109/csfw.1997.596787
|View full text |Cite
|
Sign up to set email alerts
|

Strategies against replay attacks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
45
0

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 51 publications
(45 citation statements)
references
References 9 publications
0
45
0
Order By: Relevance
“…We also suggest that practical techniques such as [6] may prove useful in making candidate protocols robust against such attacks. For example, by ensuring that the initiator challenge looks different to the respondent challenge.…”
Section: The Protocol Selectormentioning
confidence: 99%
See 1 more Smart Citation
“…We also suggest that practical techniques such as [6] may prove useful in making candidate protocols robust against such attacks. For example, by ensuring that the initiator challenge looks different to the respondent challenge.…”
Section: The Protocol Selectormentioning
confidence: 99%
“…For example, both message Cas(A |∼ N a) and Cas(A N a) are expressed by the same notation Cas (A, N a). To minimise the potential for replay attacks where 'similar' messages appear in different parts of a protocol, the messages are modified to make them distinct from one another [6]. For example, Cas(A, N a, 0) and Cas(A, N a, 1) or Cas(A, N a) and Cas(N a, A).…”
Section: Realising Idealised Protocolsmentioning
confidence: 99%
“…In this case an attacker tricks one of (or both) the principals into using a different protocol. Having generated a protocol P , techniques such as [3] may prove useful in making the protocol robust against such protocol-identity attacks. This requirement may also be expressed as additional goals that should be verified by the principles B and A, respectively,…”
Section: −1mentioning
confidence: 99%
“…or suggesting one should use different encryption systems or add hashings to each message, e.g. [6,3]. Protocol designers are often unwilling to follow these guidelines.…”
Section: Introductionmentioning
confidence: 99%