[Bug 213092] tar(1) continues to run and error after non-existent file

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Oct 4 11:44:56 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213092

--- Comment #2 from commit-hook at freebsd.org ---
A commit references this bug:

Author: mm
Date: Tue Oct  4 11:44:24 UTC 2016
New revision: 306669
URL: https://svnweb.freebsd.org/changeset/base/306669

Log:
  Update vendor/libarchive to git 024be27d1b299c030e8841bed3002ee07ba9eedc

  Important vendor bugfixes (relevant to FreeBSD):
  #747: Out of bounds read in mtree parser
  #761: heap-based buffer overflow in read_Header (7-zip)
  #784: Invalid file on bsdtar command line results in internal errors (1)

  PR:           213092 (1)
  Obtained from:        https://github.com/libarchive/libarchive

Changes:
  vendor/libarchive/dist/Makefile.am
  vendor/libarchive/dist/cat/test/main.c
  vendor/libarchive/dist/cat/test/test.h
  vendor/libarchive/dist/cpio/test/main.c
  vendor/libarchive/dist/cpio/test/test.h
  vendor/libarchive/dist/examples/minitar/minitar.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_7zip.c
  vendor/libarchive/dist/libarchive/archive_read_support_format_mtree.c
  vendor/libarchive/dist/libarchive/test/CMakeLists.txt
  vendor/libarchive/dist/libarchive/test/main.c
  vendor/libarchive/dist/libarchive/test/test_acl_freebsd_nfs4.c
  vendor/libarchive/dist/libarchive/test/test_read_format_mtree_crash747.c
 
vendor/libarchive/dist/libarchive/test/test_read_format_mtree_crash747.mtree.bz2.uu
  vendor/libarchive/dist/libarchive/test/test_read_set_format.c
  vendor/libarchive/dist/tar/subst.c
  vendor/libarchive/dist/tar/test/main.c
  vendor/libarchive/dist/tar/test/test.h
  vendor/libarchive/dist/tar/test/test_option_H_upper.c
  vendor/libarchive/dist/tar/test/test_option_L_upper.c
  vendor/libarchive/dist/tar/test/test_option_U_upper.c
  vendor/libarchive/dist/tar/test/test_option_n.c
  vendor/libarchive/dist/tar/write.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-amd64 mailing list