* Documentation/topdocs/NEWS.texi: Add note about safe mode.

* input/no-notation/dos-guile.ly:
* input/no-notation/dos-ps.ly:
* input/no-notation/dos-tex.ly: New file.  These tests still FAIL.

diff --git a/ChangeLog b/ChangeLog
index eba6302d35e858cd4161a34d6c5d4c85f67292bd..37cd37b94e713550322d956c07889b3597ac8c34 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,7 +1,8 @@
 2004-01-28  Jan Nieuwenhuizen  <janneke@gnu.org>
 
        * Documentation/topdocs/NEWS.texi: Add note about safe mode.
-
+       
+       * input/no-notation/dos-guile.ly: 
        * input/no-notation/dos-ps.ly: 
        * input/no-notation/dos-tex.ly: New file.  These tests still FAIL.
        

diff --git a/Documentation/topdocs/NEWS.texi b/Documentation/topdocs/NEWS.texi
index f576d229a5e39baf754fc4796ec99eacea84477e..aab90824cc1e1d099c5a5af8ab655033afda90c7 100644 (file)
--- a/Documentation/topdocs/NEWS.texi
+++ b/Documentation/topdocs/NEWS.texi
@@ -24,7 +24,9 @@ file output is disallowed, and lilypond-bin is invoked with
 @code{--safe-mode}, the user's Guile expressions are evaluated in a
 safe environment and file inclusion is not allowed.
 
-Be warned that a DOS attack using @TeX{} or PostScript is rather easy.
+Be warned that a DOS attack using Guile, @TeX{} or PostScript is
+rather easy.
+
 (This feature is still experimental.)
 
 @item There is now a Scheme macro for defining markup

diff --git a/input/no-notation/dos-guile.ly b/input/no-notation/dos-guile.ly
new file mode 100644 (file)
index 0000000..db4ccbb
--- /dev/null
+++ b/input/no-notation/dos-guile.ly
@@ -0,0 +1,14 @@
+\version "2.1.16"
+
+\header{
+    
+    texidoc = "This should not hang lilypond --safe-mode."
+    
+}
+
+% DOS
+#(do () (#f))
+
+\score{
+    \notes c''
+}
\ No newline at end of file