swig.org lacks TLS about www HOT 14 CLOSED

If sourceforge doesn't easily support TLS we could put the website on github pages instead which has easy support for TLS on custom domains.

from www.

sf supports tls, but on another domain. I still think GH pages are better.

from www.

https://sourceforge.net/p/swig/admin/ext/https/ says (my emphasis):

Your virtual hosts (swig.org, etc) can be upgraded to PHP 7.x if you change the DNS records to point to 204.68.111.101 or for subdomains CNAME vhost2.sourceforge.net. They can be configured to use HTTPS by requesting it in a support ticket.

So it seems we could just get this to work by opening a support ticket.

@wsfulton Since you recently gave me admin on the sourceforge project, I can probably make that request - OK with that?

Having TLS for swig.org would make the download links more trustable, which would be especially beneficial as we don't seem to sign releases or provide checksums for the tarballs.

from www.

@ojwb, that will be very helpful, thanks.

from www.

I've opened a ticket: https://sourceforge.net/p/forge/site-support/23342/

I also noticed that DNS is currently pointing swig.org and www.swig.org at 216.105.38.10 (which reverse resolves to vhost.sourceforge.net) but the current instructions give different IP addresses to use:

https://sourceforge.net/p/forge/documentation/Custom%20VHOSTs/

When configuring the DNS you have a choice between the default pool (vhost.sourceforge.net w/IP 204.68.111.100) and the alternate pool that gives you access to PHP 7 (vhost2.sourceforge.net w/IP 204.68.111.101).

from www.

I've not heard back from SF support yet, but looking at other tickets requesting TLS support it seems that the DNS needs to point at 204.68.111.101 to be able to enable TLS, based on https://sourceforge.net/p/forge/site-support/22629/ and noting that secureprojects.sourceforge.net also resolves to 204.68.111.101.

I've tests that IP address also works for non-TLS already, using an /etc/hosts entry and the Perl LWP module, so we don't need to wait for SF support to change this, and from the response to that other ticket they can't provision until we change this so it'd be good to get this done now.

@wsfulton Are you able to configure swig.org DNS?

from www.

Confirmed:

Hello,

In order to complete your request.
Have both domains pointed to 204.68.111.101
Let us know when this is done to continue.

Sincerely,
SourceForge Support

They must really mean both hostnames not domains - i.e. swig.org and www.swig.org both need to resolve to 204.68.111.101.

from www.

@dabeaz, could you please configure swig.org as mentioned above.

from www.

Just to confirm, am I to change ALL of the following DNS records for swig.org to 204.68.111.101?

from www.

@dabeaz Definitely the first two want to point to 204.68.111.101.

I'm not sure what the wildcard entry is there for. 216.105.38.10 seems to be an old address for SF vhosts which still works but is not mentioned in the current documentation (only 204.68.111.100 and 204.68.111.101 are) so I think it makes sense to update it, but only swig.org and www.swig.org are configured as vhosts on SF - any other subdomain will presumably give an error page (e.g. http://dummy.swig.org/) so perhaps the wildcard entry is best removed entirely.

from www.

I've made this change. Let me know if any further changes need to be made.

from www.

Thanks Dave, that looks good to me now and I've asked SF support to proceed.

from www.

https://swig.org/ and https://www.swig.org/ now work (not an April Fool joke!)

from www.

So they do, nice one.

from www.