[8.x](backport #41542) Switch to base 16 for TLS serial number in packetbeat in line with ECS changes #41693
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.
Proposed commit message
This switches the
serial_number
field in packetbeat's TLS reporting to use base 16 values instead of base 10:I don't think this is a breaking change? Also note the lack of a
0x
indicator. Not sure if we care.ECS PR here: elastic/ecs#2383
Also note that this maintains the liter bypass for
dsa
, which is deprecated. Do we still need it?Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
This will alter the reported
serial_number
for TLS certs from base 10 to base 16.This is an automatic backport of pull request #41542 done by [Mergify](https://mergify.com).