>Number:         21845
>Category:       bin
>Synopsis:       pax-as-tar creates silently corrupt archives when pathnames are longen than 100 chars (tar limitation)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 10 21:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Frank Kardel
>Release:        NetBSD 1.6T
>Organization:
	
>Environment:
	
	
System: NetBSD pip 1.6T NetBSD 1.6T (PIP) #1: Sat Jun 7 17:32:04 MEST 2003 kardel@pip:/src/NetBSD/netbsd/sys/arch/i386/compile/PIP i386
Architecture: i386
Machine: i386
>Description:
	When pax creates tar archives from file systems with pathnames longer than 100 chars the archive will
	unpack with following diagnostics:
		tar: Invalid header, starting valid header search.
		tar: Invalid header, starting valid header search.
		tar: Invalid header, starting valid header search.
		tar: Invalid header, starting valid header search.
		tar: Invalid header, starting valid header search.
	But no warning/indication is given during archive creation. Badly created archives may not be noticed.
>How-To-Repeat:
	tar cf out.tar <file tree deeper than 100 chars>
	tar xf out.tar	<- watch diagnostics here.

>Fix:
	Give at least an indication of corrupt archive (msg to stderr, exit code) as the tar file
	creation is incomplete/bad.
>Release-Note:
>Audit-Trail:
>Unformatted: