On 6/27/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
> Why is there the limitation of 30 (or 900, 10000, or $n$)? How about actually
> creating a UNIX user per notebook user? This way we wouldn't have to fiddle
> with permissions but everything is secured by the trustworthy UNIX user
> model?
>
> Signing up requires some effort (we could add a captcha as a Turing test) so I
> wouldn't expect the notebook to get millions of sign-ups per second. I am not
> aware that having many (>100.000) logins on a system is like a
> Denial-of-Service (but I could be wrong here) and we might even remove all
> accounts that have been inactive for some time.

Actually, I'd be fine with people having to wait after registering until
their registration is approved by a person (e.g., me).  I mean, giving
people 100% shell access for free to a powerful computer running
a lot of software is something worth waiting an hour for.  The same
would likely go for a lot of other sys admins who would eventually run
public SAGE notebook servers.

> To further motivate this: The SAGE notebook is a free shell on a remote
> machine (plus some math stuff :-)) with no prior checks whatsoever. So it
> should be secured like a real shell  via the UNIX security model. Also, as

I totally agree.

> William wants to count active notebook users as SAGE users (which I think is
> reasonable) we should make sure that the probability of some weird script
> kidding killing all your work is way below $number_of_tries * 1/30.=

Yep.

I'm a little worried about creating new accounts for each user, just because
that means the Notebook server has to have the ability to create new accounts,
which is probably a pretty serious ability to have.  But I suppose sudo could
give them just access to the adduser command and not much else.  Actually,
I sort of like this idea.

William

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@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-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to