[Bug 1831150] Re: its undocumented that only user.* extended attributes are restored upon extraction

[Brian Murray]

Given that the only documentation which refers to the default behavior
of extended attributes is only included upstream and is not shipped in
the Debian or Ubuntu package I'm closing this bug as Invalid.

** Changed in: tar (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1831150

Title:
  its undocumented that only user.* extended attributes are restored
  upon extraction

Status in GNU tar:
  Unknown
Status in tar package in Ubuntu:
  Invalid
Status in tar package in Debian:
  New

Bug description:
  The tar info page and upstream documentation indicate that when
  --xattr is used "all names are stored in the archive (or extracted, if
  using '--extract')", however when using --xattr with extract the
  security.capability extended attributes are not restored. If one also
  uses "--xattrs-include=*" then the security.capability extended
  attributes will be restored.

  [Test Case]
  mkdir orig restore
  touch orig/file_with_capability_and_user_xattr
  setcap cap_net_raw=p orig/file_with_capability_and_user_xattr
  (eoan-amd64)root at impulse:/tmp# getfattr -m . -d orig/file_with_capability_and_user_xattr
  # file: orig/file_with_capability_and_user_xattr
  security.capability=0sAAAAAgAgAAAAAAAAAAAAAAAAAAA=
  user.testkey="testvalue"
  (eoan-amd64)root at impulse:/tmp# tar c --xattrs --acls --directory orig/ . | tar x --xattrs --acls --directory restore/
  (eoan-amd64)root at impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr
  # file: restore/file_with_capability_and_user_xattr
  user.testkey="testvalue"
  (eoan-amd64)root at impulse:/tmp# tar c --xattrs --directory orig/ . | tar x --xattrs --xattrs-include=* --directory restore/
  (eoan-amd64)root at impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr
  # file: restore/file_with_capability_and_user_xattr
  security.capability=0sAAAAAgAgAAAAAAAAAAAAAAAAAAA=
  user.testkey="testvalue"

  I think tar's extract behavior should be changed to match that of
  create so that all names are actually extracted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/tar/+bug/1831150/+subscriptions