tar acl support has strange behavior when used with --xattr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tar (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
as discovered in bug 1382632 (http://
The one that caught us there was that extracting a tar file with '--acl' that was created without '--acl' results in default acl being set on the top level extracted directory. One would expect that if the source tar file had no acl information that the extracted directory would have no 'default' acl.
I'll attach a script here that shows behavior of multiple combinations of:
tar -c [--acl / -no-acl / default]
tar -x [--acl / --no-acl / default ]
and source directories with acl, without acl and with default "default" acl.
Related Bugs:
* bug 1382632: horizon insecure key file permissions
* bug 1386237: tar strange behavior with --acl
* bug 1313550: ping broken (xattrs lost in tar extraction)
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: tar 1.27.1-2
ProcVersionSign
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 27 09:42:03 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-10-19 (1104 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: tar
UpgradeStatus: Upgraded to utopic on 2013-05-20 (525 days ago)
Changed in tar (Ubuntu): | |
importance: | Undecided → Medium |
heres output of a run of 'tmp-acl-bavior':