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
@mikejoh , this information is removed when log-level is set to AS3DEBUG, In this log-level CIS logs the request and response of AS3 and reduct the Certificate/Key information. As parsing the request and response is slightly costly operation, there may be some impact on CIS performance.
@vklohiya Thanks for the quick answer! We do indeed have the --log-as3-response flag set and log level set to DEBUG, we'll try to reconfigure these flags a bit.
Setup Details
CIS Version : 2.18.1
Build: f5networks/k8s-bigip-ctlr:2.18.1
BIGIP Version: BIG-IP 17.1.1.3 Build 0.0.5 Point Release 3
AS3 Version: 3.51 Build 5
Agent Mode: AS3
Orchestration: K8S
Orchestration Version: 1.28.13
Pool Mode: Cluster
Additional Setup details: Cilium as CNI
Description
When we've enabled
DEBUG
log in thek8s-bigip-ctlr
we can see that it outputs certificates, CA chain and private key like this:Which feels wrong, even if we're setting
DEBUG
as log level.I would not expect this since there's code that tries to remove that information from the log output (no matter which log level AFAICT):
k8s-bigip-ctlr/pkg/agent/as3/postManager.go
Lines 403 to 463 in e3c0ec4
For some reason the certificate, CA chain and private key are still passed to and outputted in logs.
Steps To Reproduce
k8s-bigip-ctlr
toDEBUG
TLSProfile
that references asecret
(we're issuing certificates viacert-manager
)Expected Result
DEBUG
level logs without sensitive information, basically not the private key.Actual Result
N/A
Diagnostic Information
N/A
Observations (if any)
The text was updated successfully, but these errors were encountered: