Hello,
I'm putting together an rdiff-backup setup, making use of the
--include-globbing-filelist option. My usage is straightforward, except for
one little twist which apparently isn't working as it should.
With an amateur eye to security, I want rdiff-backup to mirror public keys
in ~/.ssh directories---but not the private keys therein---along with
everything else in the home directories. As you know, SSH private keys are
conventionally named "id_something" (or "identity" for SSH1); the
corresponding public keys have the same name but with ".pub" appended. My
globbing-filelist, simplified and with lines numbered, is thus
1) - /proc
2) + **/.ssh/id*.pub
3) - **/.ssh/id*
4) + /home
5) - /
Lines 2 and 3 cause weirdness. Here is the behavior I have observed with
version 0.13.6, and various permutations of this filelist:
A. With the filelist as shown above: Destination directory is completely
empty except for users' public keys. /home/user/ImportantStuff/ et al.
is nowhere to be found.
B. Remove lines 2 & 3: Destination directory has a complete mirror of
/home. /home/user/ImportantStuff/ is there, but so are the users'
private keys. Not what I want.
C. Remove only line 2: Same as B.
D. Remove only line 3: Same as A.
It seems to me that either I am misunderstanding the rules by which
rdiff-backup interprets the globbing filelist (and perhaps there is a
better way to express the stated aim), or this is a bug in the program.
I have put together a tarball containing a test rig that reproduces the
above behavior; it is attached. (You'll want to unpack it in /tmp for the
hardcoded paths to work.)
Would appreciate any insight on this....
--Daniel
--
NAME = Daniel Richard G. ## Remember, skunks _\|/_ meef?
EMAIL1 = skunk < at > iskunk.org ## don't smell bad--- (/o|o\) /
EMAIL2 = skunk < at > alum.mit.edu ## it's the people who < (^),>
WWW = http://www.******.org/ ## annoy them that do! / \
--
(****** = site not yet online)
