AuthWithBadShareID.seq - Authentication Chunk is received with no shared key match
To verify that if the AUTH chunk is received with bad Shared Key
Identifier, all authenticated chunks MUST be silently discarded.
./AuthWithBadShareID.seq [-tooloption ...] -pkt ./AuthWithBadShareID.def
-tooloption : v6eval tool option
See Also: ../common/STD_PKT_COMMON.def
../common/SCTP_COMMON.def
Association is established between endpoint A and B. Arrange data
in endpoint A such that AUTH chunk with bad Shared Key Identifier
is sent to endpoint B.
Endpoint A Endpoint B ULP
(ESTABLISHED) (ESTABLISHED)
AUTH ------------------>
(with Bad Shared Key Identifier)
Silently discard
TEST DESCRIPTION:
1. Send AUTH chunk from endpoint A to B with bad Shared Key Identifier.
2. Check A: All authenticated chunks be silently discarded.
None
RFC 4895
6.3. Receiving Authenticated Chunks
The receiver has a list of chunk types that it expects to be received
only after an AUTH-chunk. This list has been sent to the peer during
the association setup. It MUST silently discard these chunks if they
are not placed after an AUTH chunk in the packet.
The receiver MUST use the HMAC algorithm indicated in the HMAC
Identifier field. If this algorithm was not specified by the
receiver in the HMAC-ALGO parameter in the INIT or INIT-ACK chunk
during association setup, the AUTH chunk and all the chunks after it
MUST be discarded and an ERROR chunk SHOULD be sent with the error
cause defined in Section 4.1.
If an endpoint with no shared key receives a Shared Key Identifier
other than 0, it MUST silently discard all authenticated chunks. If
the endpoint has at least one endpoint pair shared key for the peer,
it MUST use the key specified by the Shared Key Identifier if a key
has been configured for that Shared Key Identifier. If no endpoint
pair shared key has been configured for that Shared Key Identifier,
all authenticated chunks MUST be silently discarded.