> Just out of curiosity are you listing options like the above since
> you "want somebody to implement them", or are you listing them because
> you want to implement one of them, and you want feedback before you
> choose the one that you want to implement?
I'd be willing to implement this functio
> I think the public free Sage notebook should be configured so that
> the sageXX accounts cannot open sockets to the outside world. Period.
> If I knew how to configure this in < 30 minutes, I would have done it already.
>
> Once we nail down a reasonably secure public sage notebook configurati
Here are a few fun things that anyone can do with a public Sage
Notebook:
1. Use the Sage server as remote file storage. Take your pick between
ftp, cvs, subversion, or even brew your own protocol.
2. Host your own web site. Remember: Apache is only a wget away!
3. Are your thesis simulations
C++, or Java. In this case, sockets
would still be usable by the core libraries, but they would not be
available within the shells.
--
TrixB4Kidz
--~--~-~--~~~---~--~~
To post to this group, send em
>
> (2) The actual .py file:
> [EMAIL PROTECTED]:~/nb1$ more notebook.py
> from sage.all import *
>
> server_pool=['[EMAIL PROTECTED] -p 7000'%n for n in range(1,31)]
>
> notebook(port=8103, accounts=True, address='sage.math.washington.edu',
> secure=Tr
x27;ve been typing this message long enough. I hope to hear
from
you soon about your thoughts on these issues.
-- TrixB4Kidz
P.S. You have a few hundred defunct sage processes running on your
system.
--~--~-~--~~~---~--~~
To post
