Nils Bruin <nbr...@sfu.ca> writes: > As remarked on: > > http://wiki.sagemath.org/SageServer > > it's essentially impossible to safely run sage to natively listen on > port 80 or port 443, because these are privileged ports and sage > currently doesn't have convenient mechanisms to relinquish privileges > after opening the port. > > The solution on the above wikipage is to use Apache to set up a > forward proxy, delegating the SSL layer to Apache in the process. > > Another solution is to use "iptables nat" to forward the port: > > iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j REDIRECT -- > to-port 8000 > > Any comments on the pros and cons of these approaches? I thought one > of the pros is that iptables is virtually sure to be running already, > whereas apache might not be.
I used iptables to run our university's Sage server on external port 80 but internal port 8000. It worked, and still works, without any problems. I agree that it would be good to mention this on the wiki page. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
