Re: hdup 1.6.16 gzip/bzip issue

Miek Gieben <[email protected]> Thu, 26 Jun 2003 23:17:47 +0200
Newsgroups gmane.comp.sysutils.backup.hdup.devel
Message-ID <[email protected]>
[On 26 Jun, @16:11, Nathan wrote in "[hdup-dev] hdup 1.6.16 gzip/bz ..."]
> Hello,
> 
> would work as expected if I defined compression=bzip on both sides. So I
> did and it had the correct extension this time. I have looked over the
> documentation and couldn't find mention of this.

you're absolutely right, I didn't copy the compression from the header
hdup sends...

Either use this patch (not sure if it will apply);
--------START---------------------
diff -u -r1.7 -r1.8
--- hdupremote.c        5 May 2003 11:28:49 -0000       1.7
+++ hdupremote.c        26 Jun 2003 21:10:32 -0000      1.8
@@ -64,6 +64,8 @@
        }
 
        host[which]->date = header->date; /* copy from stdin */
+    /* forget the put something in hdup->compression [miek 26-06-2003] */
+    host[which]->compression = header->compression;
 
        /* scheme is already checked */
        hdup_archive(host[which], hdup_scheme(header->scheme));
@@ -87,7 +89,6 @@
             if ( strncmp(header->compression, TAR_NONE, strlen(TAR_BZIP)) == 0 ) 
                 tar = setup_untarcmd(host[which],header->extractdir,NULL, NONE);
 
-               
             if (host[which]->alg != NULL ) {
                     if ( strncmp(header->encryption, "y",1) == 0 ) {
                         VERBOSE("%s", "Encryption found - trying to decrypt");
@@ -122,7 +123,7 @@
             split = setup_splitcmd(host[which]);
 
         /* Skip crypto stuff in the config file. This also allows the
-         * configfiles and both ends to be identical
+         * configfiles at both ends to be identical
          */
         if ( host[which]->alg != NULL ) 
                 VERBOSE("%s","Will not encrypt archives from remote hosts - encrypt them locally");
--------END-----------------------

or get the latest and the greatest from CVS. Or wait for .17.

> commonly included in distributions. I am having to hunt down and build
> my own packages for mcrypt and libmcrypt. The second is that you can
> probably get better security in a number of ways from gpg.

maybe this will also be implemented in .17. If its easy enough,

thanks,

grtz  Miek


--
:wq!