You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: