in reply to Encrypting a Filename

If you've got the file contents hidden successfully, and you just want to obscure the file name as it passes over the network, how about making a .tar file with an arbitrarily meaningless filename? Then, you don't have to decrypt the filename, but rather just untar it. The tar is just a meaningless container/shroud.

xoxo,
Andy 

%_=split/;/,".;;n;u;e;ot;t;her;c; ".   #   Andy Lester
'Perl ;@; a;a;j;m;er;y;t;p;n;d;s;o;'.  #   http://petdance.com
"hack";print map delete$_{$_},split//,q<   andy@petdance.com   >

Replies are listed 'Best First'.
Re: Re: Encrypting a Filename
by John M. Dlugosz (Monsignor) on Jun 15, 2001 at 08:26 UTC
    Because the backup process compares current files against the backup, and only copies newer files. Given changed file X, it needs to know to look at remote file Y to see if it's older.
[reply]
      So take note of the timestamp on secretfile.dat, tar it up, and then set the timestampe on the tar to that timestamp.

      If your entire tree is done with this tar mechanism, then the backup process should work fine.

      xoxo,
      Andy 

      %_=split/;/,".;;n;u;e;ot;t;her;c; ".   #   Andy Lester
'Perl ;@; a;a;j;m;er;y;t;p;n;d;s;o;'.  #   http://petdance.com
"hack";print map delete$_{$_},split//,q<   andy@petdance.com   >
[reply]
        The timestamp is not the problem. The timestamp on the tar will naturally work just as well, anyway, without having to reset it. The problem is with the filename. If it is not 1-to-1, then it will have to open the file to check the original file name, to be sure it has the right one.

        —John

[reply]

In Section Seekers of Perl Wisdom