On 16.08.2016 14:26, Alen Hiew wrote:
> Is it possible to configure on own physical server a https Web server
> (for ex., Apache) at port 443 and obfs4 or meek bridge at same static
> global IP address and same port 443?
I've set up something like this for normal tor node (not obfs), see
nginx sit
If a pluggable transport is HTTP(S)-ish, I would expect nginx to be able
to use SNI or a Host header (or the lack) to decide whether to serve web
content or proxy to tor or the transport. I'm not sure if nginx can
decide to proxy tcp based on SNI, but it would be worth reading the docs.
If this is
Something like this exists: sslh[1], a "protocol demultiplexer".
However, it doesn't explicitly support Tor, and I'm not sure if it's
possible to distinguish between Tor packets and other TLS traffic using
the options it offers[2].
[1]: http://www.rutschle.net/tech/sslh.shtml
[2]: https://github.c
I don't think you will be able to bind two daemons to the same TCP port
(443).
Maybe you could have something else listening on TCP port 443 and passing
the requests onto both places?
You might be able to put a single reverse proxy in front on that port, and
have that proxy send the requests to t
Hello, listers!
Is it possible to configure on own physical server a https Web server
(for ex., Apache) at port 443 and obfs4 or meek bridge at same static
global IP address and same port 443?
It's something like SNI, not for two TLS web sites with different domain
names at same IP but for web si
