https://bugzilla.wikimedia.org/show_bug.cgi?id=189
Dscho <johannes.schinde...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |johannes.schinde...@gmx.de
--- Comment #55 from Dscho <johannes.schinde...@gmx.de> 2009-01-23 03:36:45
UTC ---
> LilyPond is expressive enough that it's possible to write malicious code that
> could take a long time to, or possibly never, complete.
A really rudimentary research into LilyPond's documentation would show that the
safe
mode relies on GUILEs safe mode, which has been around so long that you can be
certain that it is fleshed out.
So, a preprocessor is not needed at all.
The argument that many freely available LilyPond files do not work in safe mode
is
doubly bogus:
1) they can be fixed with relatively small effort, as most pieces should not
require
any special (and possibly unsafe) operations at all,
2) the extension is not about copying existing stuff into the wiki. It is
about
creating content collaboratively, so the unsafe features would simply not be
used.
I have to admit, though, that I am amazed how long this discussion would drag
out.
If I had known about the timely decision-making powers of the responsible
persons,
I do not know if I would have spent the time writing the extension in the first
place.
It is really a sorry story.
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
