TLS/SNI matching - unsuccessful matching is printed as well? #520
onehalf3570
started this conversation in
General
Replies: 2 comments
|
ok, it was quicker to check the code - https://github.com/yrutschle/sslh/blob/e5d7cd0575d61bfe4d7687018432d60976f45e2f/tls.c#L280C41-L280C49 so it is so fixed this. But I'd suggest changing the log level to msg_probe_info, as matcher iteration is basically info, not an error |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to reduce the log clutter (main thing was to change the verbose* values from 3 to 2 in order to not have log entries coming both from syslog and from stdout redirection to syslog by systemd(?))
However, I still get a sort of duplicated 'matching' entries. I have two web servers behind the sslh - one which responds to fqdn.name and another - to www.fqdn.name
However, when I open the connection to www.fqdn.name and gets routed correctly (port 80, config is below), I still see the request getting matched with fqdn.name 🤔
Does it mean that it got matched somehow (despite working properly) or is it just a debug print (how to turn it off? verbose-connections? I would still like to see the third print, which is 'connection from ... forwarded ..')
All reactions