| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
not arbitrary values < 0.
|
|
|
|
| |
the pax-specific functions in cache.c. OK guenther@
|
| |
|
|
|
|
|
| |
on any sensible posix system (in which time_t must be an integer type)
ok deraadt@ millert@
|
|
|
|
| |
with hint from millert@; ok millert@ guenther@
|
| |
|
|
|
|
|
|
| |
group_from_gid(). Eliminate some superfluous strncpy() calls.
ok millert@
|
|
|
|
|
|
| |
both ILP32 and LP64.
ok millert@
|
|
|
|
|
|
|
| |
function names to match. Pull some tangled assignments out of conditions
and use >>= where possible.
ok millert@
|
|
|
|
|
|
|
| |
split it on a slash other than the leading one.
Fix based on patches from Peter Fokker (openbsd (at) berestijn.nl) and
Peter Bisroev (peter (at) int19h.net)
|
|
|
|
| |
ok millert@
|
|
|
|
|
|
| |
pax-like -o write_opt=nodir.
ok millert@ otto@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Prevent an archive from esacaping the current directory by itself:
when extracting a symlink whose value is absolute or contains ".."
components, just create a zero-length normal file (with additional
tracking of the mode and hardlinks to the symlink) until everything
else is extracted, then go back and replace it with the requested
link (if it's still that zero-length placeholder).
* For tar without -P, if a path in the archive has any ".." components
then strip everything up to and including the last of them (if
it ends in ".." then it becomes ".")
This mostly follows GNU tar's behavior, except for 'tar tf' and
'tar xvf' we report the modified path that would be/was actually
created instead of the raw path from the archive
Above two fixes prompted by a report from Daniel Cegielka
(daniel.cegielka (at) gmail.com)
* For directories whose times or mode will be fixed up in the
clean-up pass, record their dev+ino and then use
open(O_DIRECTORY)+fstat() to verify that we're updating the correct
directory before using futimens() and fchmod().
* Correct buffer overflow in handling of pax extension headers,
caught by the memcpy() overlap check.
previously ok millert@ deraadt@
|
|
|
|
| |
requested by deraadt@
|
|
|
|
|
|
| |
by the memcpy() overlap check.
ok millert@ deraadt@
|
|
|
|
|
| |
problem noted by miod@
ok krw@ millert@
|
| |
|
|
|
|
| |
adjective suggested by deraadt@
|
|
|
|
| |
ok fgsch@
|
|
|
|
| |
ok guenther step
|
|
|
|
|
|
|
|
| |
wide, so they support up to 33bits. Take advantage of the extra bits by
no longer forcing them into 32bit ints before the time_t conversion. This
gets us another 204 years of range once time_t changes type
ok deraadt@ tedu@
|
|
|
|
|
|
|
|
| |
being checked after it was overwritten by the next block read in.
Eliminate the argument aliasing that led to this being overlooked
by passing rd_xheader() the size and typeflag directly.
problem discovery and ok fgsch@
|
|
|
|
|
|
| |
handled.
input from zhuk and guenther. tested by zhuk and sthen on a bulk.
ok guenther.
|
|
|
|
|
|
|
| |
issues with some crappy tar archive readers out there that rely on the
fact that directory entries ends up with "/" when created by GNU Tar, and
now I'm finishing this commit message by mentioning people who gave input
and okays: deraadt@ millert@ jmc@
|
| |
|
|
|
|
| |
tar file manipulation. with advice from guenther and jmc.
|
|
|
|
|
|
|
| |
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
|
|
|
|
| |
header are not always NUL-terminated. This means there's room for 1
more byte in those field. This effectively reverts revs 1.13 and 1.14;
ok jaredy@ millert@
|
|
|
|
|
|
| |
field is too small for foo" error messages when writing files with
negative time stamps on 64 bit archs.
ok millert@ deraadt@
|
|
|
|
|
| |
are not NUL terminated if the fill the whole field.
ok millert@ jaredy@
|
|
|
|
|
|
| |
headers to the generic pax structs. ustar is "funny" since some fields
are not always NUL terminated. Old-style tar headers and ustar
creation remains to be done. ok millert@ beck@
|
|
|
|
|
|
| |
potential non-spec compliance - the use of these fields as strings needs
to be revisited more thouroughly.
ok millert@ otto@
|
| |
|
|
|
|
| |
from espie@. ok espie@ deraadt@
|
|
|
|
| |
and use the uid/gid of nobody. Spotted by and ok drahn@, ok millert@
|
| |
|
|
|
|
|
| |
in my tree for ages but didn't have a proper test case. Thanks to
otto@ for providing one.
|
| |
|
|
|
|
| |
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
|
|
|
|
| |
o When extracting GNU tar archives, honor @LongLink long links/files
o Add an option to prevent pax from prompting for the next volume
upon premature end of archive.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
do anything else to it. This lets us restore the strlcpy() calls
and remove a buch of memset()s that were zeroing out individual
fields of the header.
|
|
|
|
| |
elements to be zero padded too.
|
|
|
|
|
|
|
|
| |
tar files we need to zero-pad the file name or many tars will get
a directory checksum error trying to unpack the archive.
This does not affect ustar archives (pax's default) though whether
or not padding matters there still needs to be determined.
|
| |
|
| |
|