Rudi De Vos wrote:Yep, back
SCIII design need to be changed.
It should use the same exe as SCII and repeater.
The SSL implementation need to run as a seperate exe and SC connect in loopback. Same on the repetaer site, the SSL part listen to 443 and connect to the standard repeater ports.
This is more flexable and a lot easier to maintain then different SC versions.
Rudi De Vos wrote:Enduser release use 2 threads, in one exe via loopback.
But during development 2 exe are just a lot easier.
posbis wrote:
Maybe the distributor service is running on a machine (on the INTRANET) where already an IIS or Apache is running on SSL port (443) for internal services but has a lot of free capacity. So I would map the firewall external port 443 to another internal port (e.g. 44343) on this machine (port forwarding with translation). In this case distributor would have to listen on port 44343.
nolazabal wrote:posbis wrote:
Maybe the distributor service is running on a machine (on the INTRANET) where already an IIS or Apache is running on SSL port (443) for internal services but has a lot of free capacity. So I would map the firewall external port 443 to another internal port (e.g. 44343) on this machine (port forwarding with translation). In this case distributor would have to listen on port 44343.
i belive you can configure a not ssl port to what ever you want and then using the regualr viewer (not ssl) to connect and since you plan for a intranet wont be much of a problem not using an ssl connection. i think for this you will have to use a repeater configured with tht ports you want
Users browsing this forum: No registered users and 2 guests