Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] How to recognize ssf protocol? #109

Open
colemar opened this issue Jun 5, 2024 · 1 comment
Open

[Request] How to recognize ssf protocol? #109

colemar opened this issue Jun 5, 2024 · 1 comment

Comments

@colemar
Copy link

colemar commented Jun 5, 2024

I need to identify the ssf protocol in order to let sslh (protocol demultiplexer by Yves Rutschle) recognize it and distinguish an ssf client connection on port 1234 from the others.
If sslh recognizes an ssf client it should forward the tcp connection to localhost:8011.

Emulating the server with the command ncat -lk 1234 | xxd I can see that when an ssf (Windows) client attempts a connection the first 11 bytes sent are always:
\x16\x03\x01\x00\x5a\x01\x00\x00\x56\x03\x03

Is this a reliable check?

@colemar
Copy link
Author

colemar commented Jun 5, 2024

After some consideration, I realized that the above mentioned 11 bytes are part of the TLS handshake, therefore they are not specific to an ssf client.

I plan now to make the ssf client connect through an existing remote stunnel4 on port 443, which already provides a secure TLS channel.
Can ssf be configured to handshake with a remote stunnel4 daemon which already uses a "Let’s Encrypt" certificate?
Cann ssfd be configured to drop the TLS layer?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant