You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user I'd like to be able to search for certificates based on SHA1 fingerprints. For example if I want to query for certificates matching a SSL blacklist like https://sslbl.abuse.ch/ then I need to have a fingerprint in Elasticsearch.
Packetbeat should probably also support SHA256 hashing as well. Some apps are moving to using that.
This patch adds support to calculate fingerprints to the TLS parser in
packetbeat. The feature is controlled by a new configuration option:
```
fingerprints: [sha1, sha256]
```
Valid values are `sha1`, `sha256` and `md5`.
Closeselastic#8180
This patch adds support to calculate fingerprints to the TLS parser in
Packetbeat. The feature is controlled by a new configuration option:
```
fingerprints: [sha1, sha256]
```
Valid values are `sha1`, `sha256` and `md5`. Default is `sha1`.
Closes#8180
As a user I'd like to be able to search for certificates based on SHA1 fingerprints. For example if I want to query for certificates matching a SSL blacklist like https://sslbl.abuse.ch/ then I need to have a fingerprint in Elasticsearch.
Packetbeat should probably also support SHA256 hashing as well. Some apps are moving to using that.
The text was updated successfully, but these errors were encountered: