Non-repudiation is duplicated?
security, terminology
Solution
Neither authentication nor integrity protections prevent replay attacks. A malicious user can capture a signed and encrypted message and post it multiple times. Therefore a party can repudiate having sent the same message multiple times.
Making each message unique using timestamps and/or nonces addresses this and is therefore used for non-repudiation in combination with signing and encryption.
Problem
When we talk about security we have the following requirements: - authentication - integrity - Non-repudiation Isn't the third requirement included in the first two? If we know A sent the message (authentication) and it has not been changed since A sent it (integrity) then how can A repudiate sending it? Please don't talk about dig-sig as it's in the technical level. I'm talking about the business requirements.