screen-profiles-export records ownership (breaks ssh into root)

The tar exported with screen-profiles-export includes an entry for '.' ($HOME) and also embeds the user name and group at export time. This, combined with tar's default behavior, results in $HOME being owned by a non-root user when the export is unpacked by root.

Steps:
1) create a screen profile using screen-profiles
2) run screen-profiles-export -f screen-export.tar.gz
3) scp screen-export.tar.gz root@machine:./
4) ssh root@machine
5) ls -ld $HOME
6) tar xzf screen-export.tar.gz
7) ls -ld $HOME

At step 7, you will notice that $HOME has changed ownership to something other than root. This will break pubkey-based ssh logins to the root account.

I suggest using --owner=root and --group=root when screen-profiles-export creates the archive. Alternately, a README.Debian notice could warn users to use tar xozf [...] instead of the more typical xzf (o = --no-same-owner) when unpacking the export.

There is no problem when unpacking into a non-root-account, since --no-same-owner is the default behavior when extracting as non-root.

This probably deserves to be a wishlist item, since people should not be logging in directly as root--much less running screen as root. The workaround is to 'chown root.root /root' and 'chown -R root.root /root/.screen*'.

This may be a time bomb waiting for users unfamiliar with ssh's strict ownership requirements for pubkey logins (bad ~ means no pubkey logins). After step 6, if you do not chown /root back before logging out, you will not be able to ssh back in as root with pubkey auth. (A workaround for that is to ssh in as a non-root user and run 'sudo chown root.root /root'.)