Sage is as secure as bash (+ compilers). If you want to run arbitrary bash scripts, let other people run their bash scripts, or set up a web interface for others to running bash scripts, then you should get your security from another level (limited accounts, jails, virtual machines, etc.)
One can talk a bit about the security of the notebook itself, which has been done, but it doesn't really make sense to talk about "sage security" as it's a (huge) superset of a shell prompt. On Thu, Mar 1, 2012 at 2:19 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2012-02-29 22:56, Jan Groenewald wrote: >> Sage now has to watch the security updates for each component. > Sage is totally insecure and watching security updates isn't going to > solve this problem. > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
