Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Examine TLV bounding #375

Open
dccutrig opened this issue Dec 17, 2024 · 1 comment
Open

Examine TLV bounding #375

dccutrig opened this issue Dec 17, 2024 · 1 comment
Assignees
@dccutrig

Comments

@dccutrig
Copy link
Contributor

Examine TLV bounding in Crypto_Process_Extended_Procedure_Pdu.

Need to ensure that TLV values in a packet are:

  1. Less than or equal to Max TLV Length (done, and fixed otherwise segfault - UTs exist) , and
  2. That TLV values make sense in the context of the length of both frames and space packets received

2 is a little more complicated and I can revisit
@dccutrig dccutrig self-assigned this Dec 17, 2024
dccutrig added a commit that referenced this issue Dec 18, 2024
@dccutrig
[#375] WIP - shows a good example of TLV actually being corrupted and…
a0d1e6b 
… deactivating a bunch of keys. Tests are being worked pre-development
@dccutrig
Copy link
Contributor Author

Behold, an example of what mismatched lengths and corrupted values can currently do - and also the point of this issue:

image

dccutrig added a commit that referenced this issue Dec 19, 2024
@dccutrig
[#375] WIP on UTs for TLV testing, rename tlv 'pdu' name to actually …
8773bcb 
…be tlv_pdu for clarity
dccutrig added a commit that referenced this issue Dec 19, 2024
@dccutrig
[#375] Wording in crypto_print for TLVs
7f941bf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dccutrig dccutrig

Labels
None yet
Projects
CryptoLib Path Forward
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dccutrig