Thanks for your help. Your suggestion led me to the problem. I am up and running now.
Part of the problem is that I am somewhat new to the MAC as well as to SAGE. Neal On Mar 8, 8:06 pm, Jason Grout <[EMAIL PROTECTED]> wrote: > Neal wrote: > > Going back to the original subject, > > > I understand that a patch has been created and approved. What is the > > next step? > > Will this patch show up in the next file version of SAGE? Is there a > > schedule of such > > versions? > > > I realize that I could choose to recompile the source, but I am not in > > a position to do that. So > > I will wait until the fix gets incorporated into the distribution. > > When does that happen? > > The patch at trac ticket #2423 has already been merged into the next > version of Sage and will available there. The next version of Sage will > hopefully be release very soon. > > That said, going back to the original post, I don't the patch will have > any effect on the original problem. The path at #2423 addresses the > security issue that the notebook server was *too* easy to access from > anywhere. If anything, the patch will make it a little harder to > connect to a notebook server (i.e., now you have to specify > notebook(address=something), whereas with 2.10.2, notebook() was > sufficient). > > Are you still having the problem noted in the original post? The fact > that you can access the laptop's web server (on port 80), but not the > sage server (on port 8000) points strongly towards a firewall issue > which nothing from within sage can change. If you are still having the > problem, have you checked the firewall on your laptop? > > Thanks, > > Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
