3 commits

Author	SHA1	Message	Date
Arne Welzel	e85a12f286	btest/files/x509/files: Sort analyzers in baseline ... This test is very sensitive to new enum values that perturb the final order of the output. Listing the commits that modify that file in the past clearly shows changes to the baseline happen when a new component with an enum value is introduced. 40f04d4ccf broker: Add WebSocketShim backend 51836d08ae protocol: Add StreamEvent analyzer fdde1e9841 cluster/serializer: Add binary-serialization-format 6fb73aa9da broker: Add shim plugin adding a backend component 85ca59484b postgresql: Initial parser implementation efc2681152 WebSocket: Introduce new analyzer and log ... That's just distraction. Point fix the test to sort the analyzers before writing the final log line. I've previously attempted this in a more complete fashion in PR #3365 (issue #3364), but seems this direct fix might just make more sense. (cherry picked from commit 2f6c31df89)	2025-07-02 18:45:47 +02:00
Benjamin Bannier	c0daacfbd1	Require have-spicy for tests which log spicy-ldap information	2023-10-10 09:21:57 +02:00
Johanna Amann	b02f22a667	Change SSL and X.509 logging format ... This commit changes the SSL and X.509 logging formats to something that, hopefully, slowly approaches what they will look like in the future. X.509 log is not yet deduplicated; this will come in the future. This commit introduces two new options, which determine if certificate issuers and subjects are still logged in ssl.log. The default is to have the host subject/issuer logged, but to remove client-certificate information. Client-certificates are not a typically used feature nowadays.	2021-06-29 09:26:43 +01:00