Does TM support shsnf_len > 0?
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 169
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
I noticed all the TM unit tests use shsnf_len=0. When I set shsnf_len=4 (as TC does), I get MAC validation failures on unprotect.
Is TM with a transmitted sequence number field supported, or should I stick with shsnf_len=0?
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the TM unprotect failure with shsnf_len=4 and compare it with the existing TM unit-test cases using shsnf_len=0. Trace the MAC validation path to determine whether transmitted sequence number fields are supported; done means the behavior is verified and the relevant tests or support guidance reflect the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100