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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support TLS-encrypted protocols over direct-tcpip #65

Open
jaksi opened this issue Jul 27, 2021 · 2 comments
Open

Support TLS-encrypted protocols over direct-tcpip #65

jaksi opened this issue Jul 27, 2021 · 2 comments

Comments

@jaksi
Copy link
Owner

jaksi commented Jul 27, 2021

For HTTPS and eventually SMTP, POP3 and IMAP over TLS (#64).
We'll obviously have to use some invalid self-signed cert but maybe attackers won't notice? 馃憖 One way to find out.

@Kofl
Copy link

Kofl commented Aug 6, 2022

You could integrate e.g. let's encrypt for valid TLS certificates.

@jaksi
Copy link
Owner Author

jaksi commented Aug 29, 2022

Thanks for the suggestion!

Since attackers are expected to try and use TCP/IP forwarding to connect to domains we do not control (like an email service), and since Let's Encrypt (and all other trusted CAs) require domain ownership to request and create valid certificates, I don't think this is feasible.
I think the best we can do is create untrusted, self-signed certificates on-demand.

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

2 participants