🐛 [BUG] - Fix Key Verification IV values

[dccutrig]

Description

Currently keyv just increments a counter, research this a little further and likely need to use the active SA IV (either SA 0 or max for EPs)

I was looking at Crypto_Increment, it only does an increment of +1 on each call. In this example we have a + x + 1... which I think is just so they are all unique. If we use the existing crypto_increment, without the + x, we'd either have to use a for loop X times to increment, or re-write the UTs using it.

Are there any issues with the proposed change along the lines of:

for ( int j=0; j<x; j++ )
{
Crypto_Increment(sdls_ep_keyv_reply.blk[x].iv, SDLS_IV_LEN);
}

I'm unclear on what the second increment could / should be for the line:

sdls_ep_reply[pdu_data_idx - 1] = sdls_ep_reply[pdu_data_idx - 1] + x + 1;

REVIEW this and update.

Branch Name

No response

Reproduction steps

Not blank

Screenshots

![DESCRIPTION](LINK.png)

Logs

OS

Linux

[Donnie-Ice]

I don't see the need for the crypto_increment() to be in a for loop, but the function call itself looks good. For the second increment, you maybe able to call crypto_increment(&sdls_ep_reply[pdu_data_idx - SDLS_IV_LEN], SDLS_IV_LEN)