On Sun, Oct 26, 2014 at 07:59:55PM +0100, René Scharfe wrote: > Am 23.10.2014 um 03:09 schrieb brian m. carlson: > >The pax format is an extension of the tar format. All of the pax > >implementations I've seen on Linux (OpenBSD's and MirBSD's) don't > >actually understand the pax headers and emit them as files. 7zip does > >as well. I expect there are other Unix systems where tar itself doesn't > >understand pax headers, although I don't have access to anything other > >than Linux and FreeBSD. > > NetBSD's tar does as well. > > It's surprising and sad to see *pax* implementations not supporting pax > extended headers in 2014, though. It seems long file names etc. are not > common enough. Or perhaps pax is simply not used that much. The original pax utility didn't specify the pax format, only cpio and ustar. The pax format was first release in POSIX 1003.1-2001. > >Since it's very common to extract tar archives in /tmp, I didn't want to > >leave world-writable files in /tmp (or anywhere else someone might get > >to them). While the contents probably aren't sensitive, a malicious > >user might fill someone's quota by "helpfully" appending /dev/zero to > >the file. And yes, users do these things. > > The extracted files are only world-writable if umask & 2 == 0 or if -p > (preserve permissions) has been used, no? Yes, unless you're the superuser, in which case that's the default. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Attachment:
signature.asc
Description: Digital signature