That one can write a program that uses arbitrarily large amounts of memory
is totally expected. In python, one can do:
L=[0]
while True:
L.extend(L)
it's really the responsibility of the operating system to decide if the
relevant user should have the privilege to grind the system to a halt. In a
unix environment where you want to protect against runaway jobs, this can
be done with per-process resource limits. This would fall under that
category. If you also want to protect against DOS by multiple processes,
nowadays you'd probably give the person a VM with intentionally limited
memory and swap.
The ticket is probably still a bug so it's worth solving, but it doesn't
have particular security status in my opinion.
On Monday, 2 August 2021 at 05:24:18 UTC-7 emanuel.c...@gmail.com wrote:
> This ticket <https://trac.sagemath.org/ticket/32325>, result from this
> ask.sagemath question
> <https://ask.sagemath.org/question/58202/system-eqs-eq-with-abs-then-solve-kills-the-kernel/>,
>
> may be worth some special attention : it shows a way for Sage to grab all
> available memory, and possibly take the whole system down by memory
> starvation.
>
> HTH,
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/4ce529cc-ccfa-4c63-aaad-622336b0d9c5n%40googlegroups.com.
