On Tue, 06 Mar 2012 at 12:53PM -0800, Mike OS wrote: > I'd like to set up a sage notebook server at my campus. Since this is > beyond my expertise, I asked the College IT specialists to handle it. > Of course, they are very concerned about vulnerabilities, so they will > only allow access from on campus.
That's probably a wise idea. > 3. The part of the "how-to" instructions that leave me coldest are the > "here is where we create the accounts sage1 ... sageN" on the server > and try our best to keep people from exploiting them. They even go as > far as talking about filesystem ACLs ... which tells me we don't want > to go anywhere near this. > > So, my question to you, as someone who hopefully understands the > desired > outcome better than I, is: > > Does a sage notebook server require interactive logins? I'm thinking, > but am not quite sure, that the interactive logins are for students to > run sage from a command line, and as long as one creates sufficient > accounts in the notebook server itself (not accounts on the host where > the notebook server is hosted) the notebook server can exist without > interactive logins. The mathematician in me wants to say, the computer won't be very useful if no one can log in and interact with it. So yes, it requires interactive logins. :) I think the answer your IT person wants is: no, the "sageN" accounts don't need to be remotely accessible, but since the users will be given a full Python process in those accounts, they can do most things that an interactive login would give them, since they can use os.system() and the subprocess module, can fork bomb the server, and so on. Dan -- --- Dan Drake ----- http://mathsci.kaist.ac.kr/~drake -------
signature.asc
Description: Digital signature
