Robert and Tim,
Thanks for your responses. Perhaps it is time I start reading the Sage
Developer's Guide. :)
-- Kyle
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTEC
On Oct 18, 2008, at 4:41 PM, Kyle wrote:
> William,
>
> Do you think that in the meantime Sage could be setup without any
> shell access? I always wondered why any Joe Schmoe could log in, and
> run arbitrary shell commands... Can 'sh' be disabled? Perhaps Sage
> should be running in a chroot jai
On Sat, Oct 18, 2008 at 7:41 PM, Kyle <[EMAIL PROTECTED]> wrote:
>
> William,
>
> Do you think that in the meantime Sage could be setup without any
> shell access? I always wondered why any Joe Schmoe could log in, and
> run arbitrary shell commands... Can 'sh' be disabled? Perhaps Sage
> should b
William,
Do you think that in the meantime Sage could be setup without any
shell access? I always wondered why any Joe Schmoe could log in, and
run arbitrary shell commands... Can 'sh' be disabled? Perhaps Sage
should be running in a chroot jail?
Sadly, the easiest way the cracker could have tak
On Tue, Oct 14, 2008 at 8:26 PM, Jason Grout
<[EMAIL PROTECTED]> wrote:
>
>>
>> Actually, the concept Timothy is talking about is true. The framework
>> for running notebook processes in Knoboo is very different from what
>> Sage does to serve notebooks. Indeed, the machine running actual
>> noteb
On Tue, Oct 14, 2008 at 2:13 PM, Dorian Raymer <[EMAIL PROTECTED]> wrote:
> Hi,
> This is a good discussion. It's interesting to see, after all this time, the
> public notebook being attacked! (exclaimed in the most respectful, positive,
> excited that now this problem really has to be solved mano
On Mon, Oct 13, 2008 at 3:31 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On Oct 13, 3:05 pm, "Timothy Clemans" <[EMAIL PROTECTED]>
> wrote:
>
> Hi Timothy,
>
>> I had never heard of "fork bomb" until now. According to Wikipedia,
>> it's somewhat preventable by implementing a limit of the number of
>
> Actually, the concept Timothy is talking about is true. The framework
> for running notebook processes in Knoboo is very different from what
> Sage does to serve notebooks. Indeed, the machine running actual
> notebook processes (or engine processes as we call them) is considered
> histo
Hi,
This is a good discussion. It's interesting to see, after all this time, the
public notebook being attacked! (exclaimed in the most respectful, positive,
excited that now this problem really has to be solved manor :)
Over the last few months I've been thinking about and working on the
problems
On Tue, Oct 14, 2008 at 1:06 AM, Serge Salamanka <[EMAIL PROTECTED]> wrote:
>
> I have experience with Xen.
> Can set up a virtual machine for Sage.
> It's not that difficult anyway.
What do you need to do this? How secure are they?
By the way, I'm currently copied all the data from sagenb.org
> A security researcher decided to purposely take down sage.math to
> demonstrate that it is possible to fork bomb the machine through the
> public sage notebook servers. I had always plan to run these comletley
> public servers until something like this happened. Therefore,
> sagenb.org (and t
Jason Grout wrote:
> William Stein wrote:
>> Hello,
>>
>> A security researcher decided to purposely take down sage.math to
>> demonstrate that it is possible to fork bomb the machine through the
>> public sage notebook servers. I had always plan to run these comletley
>> public servers until
William Stein wrote:
> Hello,
>
> A security researcher decided to purposely take down sage.math to
> demonstrate that it is possible to fork bomb the machine through the
> public sage notebook servers. I had always plan to run these comletley
> public servers until something like this happe
On Oct 13, 3:05 pm, "Timothy Clemans" <[EMAIL PROTECTED]>
wrote:
Hi Timothy,
> I had never heard of "fork bomb" until now. According to Wikipedia,
> it's somewhat preventable by implementing a limit of the number of
> processes per user.
just read "man ulimit" :)
> I like the fact that Knoboo
I had never heard of "fork bomb" until now. According to Wikipedia,
it's somewhat preventable by implementing a limit of the number of
processes per user.
I like the fact that Knoboo makes it easy to run the actual Sage
processes on a completely different machine or at least in a virtual
machine.
William Stein wrote:
> Hello,
>
> A security researcher decided to purposely take down sage.math to
> demonstrate that it is possible to fork bomb the machine through the
> public sage notebook servers. I had always plan to run these comletley
> public servers until something like this happe
On Monday 13 October 2008, William Stein wrote:
> Hello,
>
> A security researcher decided to purposely take down sage.math to
> demonstrate that it is possible to fork bomb the machine through the
> public sage notebook servers.
Those 'security researchers' are also known as script kiddies.
W
17 matches
Mail list logo
