CHANGES

   1 $Id: CHANGES,v 1.67 2000/06/30 09:00:38 stelian Exp $
   2
   3 Changes between versions 0.4b17 and 0.4b18 (released June 30, 2000)
   4 ===================================================================
   5
   6 1.      Fixed a potential buffer overflow in restore. Thanks
   7         to Stan Bubrouski <satan@fastdial.net> for reporting
   8         the bug.
   9
  10 2.      Fixed a readline-related bug which prevented
  11         'cat DUMPFILE | restore -i -f -' from working. Thanks
  12         to Charles Karney <karney@users.sourceforge.net>
  13         for the bug report.
  14
  15 3.      Changed a few "panic" into "exit", causing restore to
  16         be more stable against some attacks (like the last one
  17         reported on Bugtraq, although the last version of restore
  18         was not vulnerable - just dumped core). Thanks to
  19         Andreas Hasenack <andreas@conectiva.com.br> for reporting
  20         the bugs to me.
  21
  22 4.      Removed the suid-root bit on dump and restore in the
  23         default build (and generated RPMs). It should be safer
  24         now. Users who need the suid-root capabilities in order
  25         to make network backups should read first the man page
  26         of dump and enable the suid bit manually.
  27
  28 Changes between versions 0.4b16 and 0.4b17 (released June 1st, 2000)
  29 ====================================================================
  30
  31 1.      The -F script is called now *only* at the end of a tape,
  32         not at the end of the dump. Thanks to Christian Haul
  33         <haul@informatik.tu-darmstadt.de> for the bug report.
  34
  35         Normally, the device name and the current volume number
  36         are passed on the command line of the script. However,
  37         if you want the old style script (with no arguments
  38         passed on the command line), you can enable it in
  39         configure with the --enable-oldstylefscript.
  40
  41 2.      Use posix signal handling to preserve dump functionality
  42         with libc5. Thanks to Jeff Johnson <jbj@redhat.com> for
  43         the patch.
  44
  45 3.      Made the exit code of restore in case of a 'C'ompare
  46         command reflect the result of the compare. An exit status
  47         of 0 means the dump archive is correct, 1 means tape errors,
  48         2 means that some files were modified. Thanks to Kenneth Porter
  49         <shiva@well.com> for the suggestion.
  50
  51 4.      Made (finally) quotes work in interactive restore.
  52
  53 5.      Small fixes in order to allow dump to compile with a
  54         really old e2fsprogs version. Thanks to Ian Zimmerman
  55         <itz@speakeasy.org> for the bug report.
  56
  57 6.      Add GNU readline capabilities to interactive restore.
  58         Use configure's --enable-readline flag to enable this feature.
  59         Thanks to Patrik Schindler <poc@pocnet.net> for the
  60         suggestion.
  61
  62 7.      Do the compare on the fly in restore 'C' mode (this will
  63         allow not to exhaust the available /tmp space when
  64         ccmparing large files). Thanks to Kenneth Porter
  65         <shiva@well.com> for the suggestion.
  66
  67 Changes between versions 0.4b15 and 0.4b16 (released March 11, 2000)
  68 ====================================================================
  69
  70 1.      Fixed some several duplicate 'DUMP: DUMP:' in the
  71         output of dump.
  72
  73 2.      Corrected the estimation of blocks to dump. Note that
  74         this is still wrong for large directory inodes, due
  75         to the size of a BSD directory entry on the tape
  76         (estimation is based on the size of the ext2 directory,
  77         which is smaller because it doesn't contain the null
  78         character at the end).
  79
  80 3.      Made dump report the total number of MB written to
  81         tape at the end of run. Thanks to W. Reilly Cooley
  82         <wcooley@nakedape.cc> for the patch.
  83
  84 4.      Added the -X option to restore giving the possibility
  85         to read the names of the files to be extracted/listed
  86         from a text file (in addition of the command line).
  87         Thanks to Dejan Muhamedagic <dejan@quant-x.com> for the
  88         patch.
  89
  90 5.      Added the device name and the current volume number
  91         as arguments to the end of tape script (dump -F option).
  92
  93 6.      Made the multi-volume dump work again (after having
  94         broken it in 0.4b15).
  95
  96 Changes between versions 0.4b14 and 0.4b15 (released March 2, 2000)
  97 ===================================================================
  98
  99 1.      Added a prompt command in interactive restore mode. Thanks
 100         to Andreas Dilger <adilger@home.com> for the patch.
 101
 102 2.      Fixed a buffer overflow problem in dump (caused by
 103         not checking the size of the filesystem parameter).
 104         Thanks to Kim Yong-jun <loveyou@hackerslab.org> for
 105         reporting this on Bugtraq (and to several dump users
 106         who forwarded me his mail).
 107
 108 3.      Added the '-F script' option to dump in order to
 109         launch a script at the end of each tape (to be used
 110         with a tape changer, or to notify the sysadmin by
 111         pager etc.).
 112
 113 4.      Fixed a bug in restore compare code caused by the changes
 114         I made in 0.4b14.
 115
 116 5.      Fixed the treatment of options using the old BSD syntax
 117         in both dump and restore.
 118
 119 Changes between versions 0.4b13 and 0.4b14 (released February 10, 2000)
 120 =======================================================================
 121
 122 1.      Fixed a bug in dump which may have caused invalid deleted
 123         directories to be dumped out if they were deleted after the
 124         mapping pass. This could occure on active filesystem and lead
 125         to heap corruption (causing dump malfunction in many possible ways).
 126         Thanks to Jan Sanislo <oystr@cs.washington.edu> for finding this
 127         bug and submitting the patch.
 128
 129 2.      Fixed the handling of the filesystem parameter in dump. A
 130         '/mnt/disk' parameter caused the disk contents to be dumped,
 131         but a '/mnt/disk/' parameter caused the mountpoint directory
 132         to be dumped (generally an empty directory).
 133
 134 3.      Improved the output of dump in order to tell which directory
 135         it is currently dumping (when dumping a subtree).
 136
 137 4.      Added the '-e' exclude inode option to dump. Thanks to
 138         Isaac Chuang <ike@isl.stanford.edu> for contributing with the patch.
 139
 140 5.      Added a REPORTING-BUGS file in order to provide a guide
 141         on how to correctly report a bug in dump/restore.
 142
 143 6.      Fixed a restore problem when restoring a hard link to an inode
 144         having the immutable or append-only attribute set. Thanks to
 145         Ambrose Li <acli@mingpaoxpress.com> for submitting the patch.
 146
 147 7.      Fixed a compatibility problem between dumps made on little
 148         endian machines (the format was correct) and big endian
 149         machines (the format was incorrect). This fix break the
 150         compatibility with the older dumps made on big endian
 151         machines (sparc, m86k, ppc etc). For the first time in
 152         linux dump's history (I believe), the dumps made by *BSD,
 153         Linux/alpha, Linux/sparc and Linux/x86 are compatible,
 154         so interchangeable. Thanks to Rob Cermak
 155         <cermak@ahab.rutgers.edu> for submitting the bug and
 156         helping me test the fix.
 157
 158 8.      Fixed the way dump reports the remaining percent/time, if
 159         the number of blocks actually dumped exceeds the estimated
 160         number of blocks. Thanks to Jean-Paul van der Jagt
 161         <jeanpaul@dutepp0.et.tudelft.nl> for reporting the bug.
 162
 163 Changes between versions 0.4b12 and 0.4b13 (released January 21, 2000)
 164 ======================================================================
 165
 166 1.      Small Y2K fix in the man pages :). Thanks to Bernhard Sadlowski
 167         <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug.
 168
 169 2.      Removed the requirement to build the RPM as root from the
 170         spec file. Thanks to Christian Weisgerber
 171         <naddy@mips.rhein-neckar.de> for submitting this.
 172
 173 3.      Fixed a bug in dump related to the 'filetype' feature of ext2fs,
 174         causing dump to block when dumping really huge filesystems.
 175         Many thanks to Patrik Schindler <poc@pocnet.net> for
 176         helping me find this bug.
 177
 178 4.      Fixed the treatment for an interrupt signal when dump access
 179         the remote tape through RSH. Thanks to Christian Weisgerber
 180         <naddy@mips.rhein-neckar.de> for providing the patch.
 181
 182 5.      Fixed a bug which was causing dump/restore to display
 183         garbage characters instead of the remote host name.
 184
 185 Changes between versions 0.4b11 and 0.4b12 (released January 8, 2000)
 186 =====================================================================
 187
 188 1.      Small fix in the dump man page. Thanks to Thorsten Kukuk
 189         <kukuk@suse.de> for submitting the patch.
 190
 191 2.      Fix for the exit code when using the size estimate option of
 192         dump. Thanks to Matti Taskinen <mkt@rni.helsinki.fi> for
 193         submitting the patch.
 194
 195 3.      Handle EINTR in atomical reads/writes in dump, which was causing
 196         dump to fail on some systems. Thanks to Eric Jergensen
 197         <eric@dvns.com> for reporting the bug and submitting the patch.
 198
 199 4.      Handle more than 16 characters for the device names in dumpdates.
 200         (up to 255 now). Thanks to Rainer Clasen <bj@ncc.cicely.de> for
 201         tracking down the problem and proposing the solution.
 202
 203 5.      Fixed a bug in dump which prevented the creation of the
 204         dumpdates file when doing a 0-level dump without already
 205         having a dumpdates file. Thanks to Patrik Schindler
 206         <poc@pocnet.net> for reporting the bug.
 207
 208 6.      Changed the way dump 'S' flag reports the size estimate
 209         from number of blocks into bytes (making it compatible
 210         with the Solaris version, and simplifying things for
 211         amanda users). Thanks to Jason L Tibbitts III
 212         <tibbs@math.uh.edu> for reporting the bug.
 213
 214 7.      Fixed a compatibility problem in linux/alpha dump tape format.
 215         Now the linux/alpha dump are (again) compatible with the
 216         other dump formats. But this breaks compatibility with
 217         older dumps made on alpha. Thanks to Mike Tibor
 218         <tibor@lib.uaa.alaska.edu> for helping me in finding this bug.
 219
 220 Changes between versions 0.4b10 and 0.4b11 (released December 5, 1999)
 221 ======================================================================
 222
 223 1.      Added a '--enable-kerberos' to configure.
 224
 225 2.      Added a 'S' option to dump which determines the amount of space
 226         that is needed to perform the dump without actually doing it, similar
 227         to the Sun's ufsdump 'S' option. Patch contributed by Rob Cermak
 228         <cermak@ahab.rutgers.edu>.
 229
 230 3.      Added a 'M' multi-volume option to dump and restore which enables
 231         dumping to multiple files (useful when dumping to an ext2
 232         partition to make several dump files in order to bypass the 2GB
 233         file size limitation). The 'f' argument is treated as a prefix and
 234         the output files will be named <prefix>001, <prefix>002 etc. With
 235         the 'M' flag, restore automatically selects the right file without
 236         asking to enter a new tape each time.
 237
 238 4.      Fixed a memory leak which was causing dump to grow very big
 239         (270MB when dumping a 10GB filesystem...). Thanks to Jason
 240         Fearon <jasonf@netrider.org.au> for reporting the bug.
 241
 242 Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999)
 243 ======================================================================
 244
 245 1.      Make configure test if the system glob routines support
 246         extended syntax (ALTDIRFUNC). If not, use the internal glob
 247         routines instead of system ones. Thanks to Bernhard Sadlowski
 248         <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug
 249         and helping me resolve this and other minor libc5 compiling
 250         glitches.
 251
 252 2.      Fix a problem when dumping a ext2fs with the 'filetype'
 253         feature enabled. Thanks to Patrick J. LoPresti
 254         <patl@cag.lcs.mit.edu> for reporting the bug and to
 255         Theodore Y. Ts'o <tytso@mit.edu> for providing the patch.
 256
 257 3.      Made the nodump flag work on directories. A directory which
 258         has the nodump flag gets never dumped, regardless of its
 259         contents.
 260
 261 4.      Integrate a patch from Jeremy Fitzhardinge <jeremy@goop.org>
 262         which allows dump on an active ext3 filesystem. However, this
 263         is a "quick and dirty" patch which enables backup of an ext3
 264         filesystem through the ext2 compatibility (by ignoring the
 265         NEEDS_RECOVERY bit). The journal file is not recognized and
 266         it is dumped (it should not).
 267
 268 5.      Test the superblock compatibility flags when dumping, in order
 269         to be sure that we know how to deal with specific features.
 270
 271 Changes between versions 0.4b8 and 0.4b9 (released November 5, 1999)
 272 ====================================================================
 273
 274 1.      Use lchown instead of chown, fixing a possible security problem
 275         when restoring symlinks (a malicious user could use this
 276         to deliberately corrupt the ownership of important system files).
 277         Thanks to Chris Siebenmann <cks@utcc.utoronto.ca> for detecting
 278         this and providing the patch.
 279
 280 Changes between versions 0.4b7 and 0.4b8 (released November 3, 1999)
 281 ====================================================================
 282
 283 1.      Put dump sources under CVS, added Id tags in all files so
 284         one can use 'ident' on binary files.
 285
 286 2.      Added the dump/restore version in the usage text so one can
 287         easily verify the version he is using.
 288
 289 3.      Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes
 290         a va_start/va_end problem on linux-ppc (always call va_start
 291         va_end in pairs each time we use a vararg function).
 292
 293 4.      Added again the DT_* constants because old libc does not
 294         contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr>
 295         for submitting the bug report.
 296
 297 5.      Use ext2fs_llseek instead of llseek. With recent e2fsprogs
 298         this should enable dumping big (huge) filesystems.
 299
 300 6.      Added the RSH environment variable in order to be able to
 301         use a rsh replacement like ssh when doing remote backups (and
 302         bypass the security limitations of rcmd). Now you can do remote
 303         backups without being root (or making dump setuid root).
 304
 305 7.      Modified again the way dumpdates works. For incremental dumps,
 306         we need to read dumpdates even if we are not using 'u' option.
 307         Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
 308         this should work.
 309
 310 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
 311 ===================================================================
 312
 313 1.      Removed the 'k' flag from the restore 'about' text if kerberos
 314         was not compiled in.
 315
 316 2.      Prototyped (f)setflags from e2fsprogs and corrected the calls
 317         to them (fsetflags takes a char*, setflags an open fd!).
 318
 319 3.      (f)setflags is called only if the flags aren't empty. If the
 320         file is a special file, a warning is printed, because changing
 321         flags implies opening the device. Normally, a special file
 322         should not have any flag... (Debian bug #29775, patch provided
 323         by Abhijit Dasgupta <abhijit@ans.net>).
 324
 325 4.      Made possible to dump a file system not mentioned in /etc/fstab.
 326         (Debian bug #11904, patch provided by Eirik Fuller <eirik@netcom.com>).
 327
 328 5.      Changed the default behaviour to not create dumpdates
 329         unless 'u' option is specified. Removed the old "debian-patch"
 330         which provided the same thing. (Debian bug #38136, #33818).
 331
 332 6.      Removed all those dump*announce, since they were getting old...
 333
 334 7.      Added warning messages if dumpdates does not exist and
 335         when an inferior level dump does not exist (except for a level 0
 336         dump).
 337
 338 8.      Debugged the glob calls in interactive mode: restore used a
 339         dirent struct which was different from the /usr/include/dirent.h
 340         one (this used to work, is it a glibc2 change?), so none of the
 341         compat glob (which used /usr/include/dirent.h) or the system glob
 342         worked. Restore use now the system dirent (and the system
 343         DT_* constants), which are compatible with BSD ones.
 344
 345 9.      Added a configure flag (--with-dumpdatespath) to specify
 346         the location of dumpdates file. By default, it is
 347         /etc/dumpdates.
 348
 349 10.     Added the "AUTHOR" and "AVAILABILITY" sections and
 350         included the current date/version in man pages.
 351
 352 11.     Corrected the estimation of remaining time when
 353         the operator doesn't change the tapes quickly enough. This
 354         was an old bug, I thought I corrected it, and discovered
 355         that in fact it was corrected in two different places, so
 356         the results canceled each other...
 357
 358 Changes between versions 0.4b5 and 0.4b6 (released October 1, 1999)
 359 ===================================================================
 360
 361 1.      Integrated multiple patches from RedHat, Debian and SuSE:
 362
 363         - tweak dump/itime.c to not try to read dumpdates if the 'u' option
 364           isn't specified.
 365         - several fixes in the man pages.
 366         - update the default tape device to /dev/st0.
 367         - many updates for Linux Alpha (byte ordering, size_t etc).
 368         - buffer overruns.
 369         - use environment variable for TMPDIR (instead of /tmp).
 370         - use sigjmp_buf instead of jmp_buf (RedHat bug #3260).
 371         - workaround egcs bug (RedHat bugs #4281 and #2989).
 372         - wire $(OPT) throughout Makefile's.
 373
 374 2.      Upgrade the dump revision to 1, making possible to dump filesystems
 375         made with e2fsprogs-1.15 or newer. Nothing seems to break...
 376
 377 3.      Fix some compile warnings, prototype all functions.
 378
 379 4.      Use glibc err/glob instead of internal compatibility
 380         routines (only if available).
 381
 382 5.      Fix a compile error on Linux 2.2.7 / libc5 (5.4.44) (patch provided
 383         by Bernhard Sadlowski <sadlowsk@mathematik.uni-bielefeld.de>).
 384
 385 Changes between versions 0.4b4 and 0.4b5 (released September 22, 1999)
 386 ======================================================================
 387
 388 1.      Integrated the changes from FreeBSD-3.1-RELEASE
 389         (mostly bug fixes, buffer overruns, dump has now an "automatic
 390         tape length calculation" flag, dump/restore can use kerberos now
 391         (this is NOT tested), use environment variables for TAPE and
 392         RMT etc.).
 393
 394 2.      Integrated three RedHat patches ("glibc", "kernel" and "bread" patches)
 395
 396 3.      Corrected a bug in restore when using 'C' option with multi-volumes
 397         tapes (files splited accros two tapes give "size changed" errors
 398         when comparing).
 399
 400 4.      Corrected the long standing bug when dumping multiple tapes.
 401         This works for me, needs further testing.
 402
 403 Changes between versions 0.4b3 and 0.4b4 (released January 17, 1997)
 404 ====================================================================
 405
 406 1.      Dump now runs correctly on kernels 2.1.x
 407         Fix made by Gerald Peters <gapeters@worldnet.att.net>
 408
 409 Changes between versions 0.4b2 and 0.4b3
 410 ========================================
 411
 412 1.      Use realpath() if available
 413
 414 2.      Report statistics
 415
 416 Changes between versions 0.4b1 and 0.4b2
 417 ========================================
 418
 419 1.      Fixed the bug fix from Greg Lutz (I had made a mistake when integrating
 420         the patch)
 421
 422 2.      Fixed restore to make it able to read FreeBSD 2.x dumps again
 423
 424 3.      Fixed configure.in to correctly handle --enable-rmt
 425
 426 Changes between versions 0.3 and 0.4b1
 427 ======================================
 428
 429 1.      Integrated the changes from 4.4BSD-Lite2
 430
 431 2.      Integrated the patches from Debian and Red Hat
 432
 433 3.      Portability changes: use the __u32, __u16, __s32, and __s16 types
 434
 435 4.      Changed dump to use the Ext2fs library to get block addresses.  This
 436         should solve the endianness problem on SparcLinux.
 437
 438 5.      Created a configure.in file (shamelessly stolen from the e2fsprogs
 439         distribution's one) to use autoconf
 440
 441 6.      Fixed a few minor bugs
 442
 443 Changes between versions 0.2e and 0.2f
 444 ======================================
 445
 446 1.      Added the creation of named pipes (fifos) in restore.
 447
 448 2.      Added the -N flag in the restore manual page.
 449
 450 3.      Added the file kernel.patch which contains the llseek() optimization
 451         patch for 1.2.x kernels.
 452
 453 4.      Fixed a bug in the restoration of symbolic links: owner and group were
 454         not restored.
 455
 456 5.      Integrated some changes from FreeBSD 2.2.
 457
 458 6.      Added a call to ftruncate() after restoring each file to restore
 459         correctly files ending by a hole.
 460
 461 Changes between versions 0.2d and 0.2e
 462 ======================================
 463
 464 1.      Fixed a bug in the "set owner/mode" process.  Every file was restored
 465         with owner = root (0) and group = root/wheel/whatever (0).
 466
 467 Changes between versions 0.2c and 0.2d
 468 ======================================
 469
 470 1.      Dump is now able to backup 2GB+ filesystems.
 471
 472 2.      Dump and restore can now be linked as static binaries.
 473
 474 Changes between versions 0.2b and 0.2c
 475 ======================================
 476
 477 1.      Fixed a bug when dumping ``slow'' (i.e. normal) symbolic links.
 478
 479 Changes between versions 0.2a and 0.2b
 480 ======================================
 481
 482 1.      Really fixed the bug that I should have corrected in 0.2a.
 483
 484 2.      Enabled optimization again.
 485
 486 Changes between versions 0.2 and 0.2a
 487 =====================================
 488
 489 1.      Disabled the optimization during compilation.
 490
 491 Changes between versions 0.1 and 0.2
 492 ====================================
 493
 494 1.      Fixed a bug in fstab.c which caused a null pointer to be stored in
 495         the fs_type field (actually, I modified the file fstab.c to make it
 496         use the mntent functions).
 497
 498 2.      Dump and restore now use a 4.3 BSD compatible dump format.  Backups
 499         made by dump should be readable by the BSD restore and backups made
 500         by the BSD dump should be readable by restore.  Unfortunately, this
 501         means that the dump format has changed between version 0.1 and version
 502         0.2 :-(
 503
 504 3.      Dump is now able to backup a subtree, it is no longer limited to whole
 505         filesystems like the BSD version.
 506
 507 4.      Dump now uses ext2_llseek() so it is able to backup filesystems bigger
 508         than 2 GB.
 509
 510 Changes between versions 0.0 and 0.1
 511 ====================================
 512
 513 1.      Now create links rdump and rrestore during the `make install' step.
 514
 515 2.      Linux port specific bugs added to the manual pages
 516
 517 3.      Incorrect estimation of the number of tapes blocks fixed when doing
 518         incremental backups.
 519
 520 4.      Better ls-like format in restore in interactive mode.