-
Notifications
You must be signed in to change notification settings - Fork 703
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/needs-triageIndicates that an issue needs to be triaged by a project contributor.Indicates that an issue needs to be triaged by a project contributor.
Description
Support TLS Fingerprinting
Today there's no way to config the envoy listeners to calculate tls fingerprinting.
Both fields are default to False and the TlsInspector object is created with no parameters.
Below is a config_dump:
"listener_filters": [
{
"name": "envoy.filters.listener.tls_inspector",
"typed_config": {
"@type": "type.googleapis.com/envoy.extensions.filters.listener.tls_inspector.v3.TlsInspector"
}
}
],
Looking at the code that construct it:
// TLSInspector returns a new TLS inspector listener filter.
func TLSInspector() *envoy_config_listener_v3.ListenerFilter {
return &envoy_config_listener_v3.ListenerFilter{
Name: wellknown.TlsInspector,
ConfigType: &envoy_config_listener_v3.ListenerFilter_TypedConfig{
TypedConfig: protobuf.MustMarshalAny(&envoy_filter_listener_tls_inspector_v3.TlsInspector{}),
},
}
}
it does not take any parameters
Can we make this configurable somewhere in the contour config or httpproxy specs?
Getting the TLS fingerprint is an important use case for our upstream service for bot fighting and etc.
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/needs-triageIndicates that an issue needs to be triaged by a project contributor.Indicates that an issue needs to be triaged by a project contributor.