transform/base64: Add "set_error" to detect if buffer is valid base64 encoded content #12085
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds to the
from_base64
decode and provides an indication of whether the input buffer is properly encoded as a base64 buffer. Useset_error
and if the buffer cannot be decoded, the output buffer will be set toBASE64_ECODE_BUF
Use this rule snippet to test whether the input is not properly encoded:
Use this rule snippet to test if the input is base64 encoded:
Link to ticket: https://redmine.openinfosecfoundation.org/issues/7114
Describe changes:
set_error
to the transform's available option listset_error
is usedProvide values to any of the below to override the defaults.
link to the pull request in the respective
_BRANCH
variable.SV_REPO=
SV_BRANCH=OISF/suricata-verify#2117
SU_REPO=
SU_BRANCH=
LIBHTP_REPO=
LIBHTP_BRANCH=