Progress report.

After succesfully logging into my own notebook as admin, I started to
set up a few user accounts.  I followed the instructions in the
notebook? docstring:

          accounts      -- (default: False) if True, any visitor to
the
                             website will be able to create a new
account.  If
                             False, only the admin can create accounts
                             (currently, this can only be done by
running with
                             accounts=True for a few minutes, or on
the command
                             line with, e.g.,
                                 nb = load('./sage/sage_notebook/
nb.sobj')
                                 nb.set_accounts(True)
                                 nb.add_user("username", "password",
                                     "em...@place", "user")
                                 nb.save()

[Note that the path to sage_notebook/nb.sobj may be different than
given above.]

Specifically I did
nb = load('nb.sobj')
nb.set_accounts(True)
nb.add_user("john", "xxxxxx", "john.crem...@gmail.com", "user")
 nb.save()

and then restarted the notebook().  Now I could not login as john, nor
as admin.  Reloading the nb,sobj and doing nb.usernames() showed only
'admin', so the extra username was not saved.  And admin logins do not
work now either. (I just get a whilte screen with nothing in it at all
after  pressing the "sign in" button, while the tab shows "Error |
Sage ...]

Am I doing something stupid?

John
For example,
On 18 Aug, 05:51, Bill Hart <goodwillh...@googlemail.com> wrote:
> Ah, OK, thanks for clearing that up.
>
> Bill.
>
> On Aug 17, 7:04 pm, William Stein <wst...@gmail.com> wrote:
>
> > On Mon, Aug 17, 2009 at 4:27 AM, Bill Hart<goodwillh...@googlemail.com> 
> > wrote:
>
> > > It's ubuntu and we can open the port as we have root access (assuming
> > > John is talking about the same machine - which I am pretty sure he
> > > is).
>
> > > How secure is the notebook server these days. Is it still advised to
> > > set it up in a chroot jail (see my other post about problems I had
> > > doing that).
>
> > That was *only* for a public notebook server.  If you're using
> > secure=True and accounts=False, so only people with existing accounts
> > can us the notebook server, there is no reason to use a chroot.
>
> > Moreover, the standard wisdom in security is that it is in fact never
> > ever in any case ever a good idea to use a chroot for security
> > purposes.  Thus one should never do that for the Sage notebook.  The
> > only acceptable thing for a public server is to use a virtual machine
> > (say virtualbox or vmware).
>
> > William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to