flock -> fcntl(F_SETLK).

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 5747d64e5509643e5d6efe2191fb93daf5a824d2..ccd47e0bd51bc6c0535bd7fcd01071cd662406b6 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,26 @@
-$Id: CHANGES,v 1.188 2002/07/24 14:11:59 stelian Exp $
+$Id: CHANGES,v 1.192 2002/08/01 10:23:26 stelian Exp $
 
-Changes between versions 0.4b29 and 0.4b30 (released ????????????????)
-======================================================================
+Changes between versions 0.4b31 and 0.4b32 (released ?????????????)
+===================================================================
+
+1.     Changed dump to use fcntl(F_SETLK) style locking instead
+       of flock() when locking the dumpdates file. With the old 
+       locking scheme, a local user having read rights on the 
+       dumpdates file could be able to do a Denial of Service attack
+       on dump. In order to lock the dumpdates file with the new
+       scheme, the user would need to have write access on the file.
+       Thanks to Richard Johnson <Richard.Johnson3@ey.com> for 
+       reporting the bug (originally a bugtraq post).
+
+Changes between versions 0.4b30 and 0.4b31 (released July 30, 2002)
+===================================================================
+
+1.     Fixed rmt open flags transmission (GNU's symbolic syntax over
+       rmt) which I broke in 0.4b29. Thanks to Eros Albertazzi
+       <eros@lamel.bo.cnr.it> for reporting the bug.
+
+Changes between versions 0.4b29 and 0.4b30 (released July 25, 2002)
+===================================================================
 
 1.     Made dump print out the ext2 logical block number in case of a read
        error, which can be given as an argument to debugfs' ncheck command,