Meaning of "matching" information

[M-Stenzel]

Hi team,

thank you again, sslh saves me many bucks, and it helps to preserve our environment!

I recently upgraded to version 2.0.1, now I receive these log lines

Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain1.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain2.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain3.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain4.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [tube.xy-space.de]

This is (part of) my config file

verbose: 0;
numeric: true;
transparent: false;
timeout: 2;
user: "sslh";

listen:
(
        { host: "0.0.0.0"; port: "443"; }
);

protocols:
(
        { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain1.xy-space.de" ]; log_level: 0; tfo_ok: true },
        { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain2.xy-space.de" ]; log_level: 0; tfo_ok: true },
        { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain3.xy-space.de" ]; log_level: 0; tfo_ok: true },
        { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain4.xy-space.de" ]; log_level: 0; tfo_ok: true },
        { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "tube.xy-space.de" ]; log_level: 0; tfo_ok: true },

The "tube.xy-space.de" is the last entry in the config file, does it take precedence? Is this intended?

The subdomain1 to subdomain4 work perfectly.

Do I have to worry?

Martin.

P. S. "subdomain1" to "subdomain4" are only substitutes to different subdomains, I do not want to give too detailed information on my setup in this post...

[Yves Rutschle]

How does it save it the environment? :D Default behavior is to connect to the last protocol entry if none match. If this is not wanted, you can add a probe called 'anyprot' that always matches (so, use it last!) The logs you're getting are just from the TLS probe checking the various domains. You're getting them now because the configuration file has changed for verbose, check out example.cfg. 12 janv. 2024 15:57:24 M-Stenzel ***@***.***>:

…

Hi team, thank you again, sslh saves me many bucks, and it helps to preserve our environment! I recently upgraded to version 2.0.1, now I receive these log lines *Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain1.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain2.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain3.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [subdomain4.xy-space.de] Jan 12 16:47:07 terve.xy-space.de sslh[19499]: matching [tube.xy-space.de] with [tube.xy-space.de]* This is (part of) my config file `verbose: 0; numeric: true; transparent: false; timeout: 2; user: "sslh"; listen: ( { host: "0.0.0.0"; port: "443"; } ); protocols: ( { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain1.xy-space.de" ]; log_level: 0; tfo_ok: true }, { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain2.xy-space.de" ]; log_level: 0; tfo_ok: true }, { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain3.xy-space.de" ]; log_level: 0; tfo_ok: true }, { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "subdomain4.xy-space.de" ]; log_level: 0; tfo_ok: true }, { name: "tls"; host: "127.0.0.1"; port: "2443"; sni_hostnames: [ "tube.xy-space.de" ]; log_level: 0; tfo_ok: true },` The "tube.xy-space.de" is the last entry in the config file, does it take precendence? Is this intended? The subdomain1 to subdomain4 work perfectly. Do I have to worry? Martin. — Reply to this email directly, view it on GitHub[#423], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABGAU74FOMVTASPIK6LZVNTYOFFM7AVCNFSM6AAAAABBYIKUNCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3TSMBTGUZDMNQ]. You are receiving this because you are subscribed to this thread. [Image de pistage][https://github.com/notifications/beacon/ABGAU77F7PAAX3FXQYSD7PTYOFFM7A5CNFSM6AAAAABBYIKUNCWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHHX24PQI.gif]

[M-Stenzel]

Thanks for clarifying,

well as to the environment... sslh makes it possible to run many web servers on one physical (or virtualized) server, thereby installation of several physical servers is not needed anymore, this helps our environment a lot - thank you!