Open perguth opened 2 months ago
Not sure if I understand your intention fully here. Can you please expand a bit on your setup / usecase? Yggstack provides SOCKS5 server and it is up to HTTP client to request HTTPS or HTTP.
yggstack (and yggdrasil in general) operate at tunnel-level concept. You mix L7 (application) OSI layer where HTTP/S resides with L3 (network) layer where Ygg operates. What you really likely want is to forward port 443 to yggstack: --exposetcp 443:127.0.0.1:443
Ah, no, my idea is not to expose the host machine. My focus is on webbrowsing (using Yggstack purely as a SOCKS proxy).
Idea:
Automatically provide HTTPS for HTTP content from Ygg-IPs:
Why?
🡆 If Yggstack install a root certificate and then generates certificates for Ygg-IPs and HTTPS-wraps the HTTP traffic, we would achieve a "valid" certificates for Ygg-IPs automatically.
HTTPS is needed for a secure context which is a Window or Worker for which certain minimum standards of authentication and confidentiality are met. Many Web APIs and features are accessible only in a secure context. Eg.: