On Friday, June 8, 2012 5:33:48 AM UTC+1, William wrote:
>
> > Maybe its also worth looking into authbind . I use it for quite a while
> now
> > to run sage.mderickx.nl nativily on a privaliged port. authbind is a
> linux
> > tool which allows you to configure which non privaleged users can use
On Thu, Jun 7, 2012 at 7:23 PM, Maarten Derickx
wrote:
>
>
> Le jeudi 7 juin 2012 05:20:02 UTC+2, Nils Bruin a écrit :
>>
>> 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 ar
Le jeudi 7 juin 2012 05:20:02 UTC+2, Nils Bruin a écrit :
>
> 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
On 6/6/12 10:20 PM, Nils Bruin wrote:
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
Just double-checking: this means that you run with secure=True, and the
notebook itself does the SSL, right
Nils Bruin 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 o
On 6/6/12 10:20 PM, Nils Bruin wrote:
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
a
