Transparent Security is a solution for identify the source devices of a DDoS attack and mitigates the attack in the customer premises or the access network. This solution leverages a P4 based programmable data plane for add in-band network telemetry (INT) for device identification and in-band mitigation.
Fixes #355
Changed from md5 to first 16 bytes of sha256 hash value
Added validation drop report hash key value
Stubbed out methods and made minor fixes to address issues #354 & #351
Do you have any concerns with this PR?
Only that we are now only taking the first 16 bytes of a sha256 hash but this should now work with snaps-hcp
How can the reviewer verify this PR?
Ensure CI does not fail
Any background context you want to provide?
snaps-hcp cannot hash with md5 and must use sha256 (or sha1) instead
Screenshots or logs (if appropriate)
Questions:
Have you connected this PR to the issue it resolves? yes
Does the documentation need an update? no
Does this add new dependencies? no
Have you added unit or functional tests for this PR? added more validation to the drop report test
What does this PR do?
Fixes #355 Changed from md5 to first 16 bytes of sha256 hash value Added validation drop report hash key value Stubbed out methods and made minor fixes to address issues #354 & #351
Do you have any concerns with this PR?
Only that we are now only taking the first 16 bytes of a sha256 hash but this should now work with snaps-hcp
How can the reviewer verify this PR?
Ensure CI does not fail
Any background context you want to provide?
snaps-hcp cannot hash with md5 and must use sha256 (or sha1) instead
Screenshots or logs (if appropriate)
Questions: