Re: rsyncrypto with --backup-dir like in rsync

[Shachar Shemesh <shachar@sh...>]

On 30/12/14 07:28, Zurd wrote:
> The original rsync has an option --backup that works with
> --backup-dir. When they are used, all the modified and/or deleted
> files are put in the --backup-dir argument.
>
> When using the --delete option at the same time, the destination
> folder is then always kept as a perfect copy like the source folder.
> And the --backup-dir folder has all the modified/deleted files in it.
>
> An example of that command would be:
> rsync --archive --delete --backup
> --backup-dir=/home/user/backup-2014-12-30/  /home/user/backup-source/ 
> /home/user/backup-destination/
>
> Does rsyncrypto has an option like that?
>
>
rsyncrypto does not have an option like that. Truth be told, rsyncrypto
was mostly designed to be a preparation step before performing rsync,
and rsync's options cover these needs quit nicely.

Hope this helps,
Shachar

Re: Having rsync issues when modified part of file isnt at end

[Shachar Shemesh <shachar@sh...>]

rsyncrypto compresses as part of the encryption. You obviously did not
notice this, as you were using /dev/random as your source, and hence
producing uncompressible files. This is also the reason (at least part
of it) that the encrypted files were not the same size.

On 03/02/15 10:34, Guillaume Friloux wrote:
> The only thing i can see is that between file1.iso.enc and 
> file2.iso.enc,
> the filesize dropped a little, and between file2.iso.enc and 
> file3.iso.enc it is higher,
> but i have no idea if this can be related...
You are using rsync with --inplace. In that mode, rsync cannot reuse
blocks that were already overwritten by the destination file. When the
new file is bigger than the old one, you are overwriting the data you
would reuse while transferring, severely limiting rsync's ability to
optimize your transfer. If you remove --inplace, you will see that rsync
has no problem optimizing your encrypted files, no matter the size changes.

You have not asked your gzip question, but I am guessing it is either
the same issue there, or you forgot to pass it the --rsyncable flag.

Shachar

Having rsync issues when modified part of file isnt at end

[Guillaume Friloux <guillaume@fr...>]

Hello everyone!

I am having an issue with the backup of a few files here, taking more 
space than need on my ZFS dataset.
After some digging, i found the issue is primarly caused by both gzip 
and rsyncrypto.

Here, i will only discuss of the rsyncrypto part making rsync to fail at 
backup efficiently :

Suppose you make 2 files of 450MB, with only 50MB that changed, in the 
middle of the file (no deleted or added data, not even moved).
To create a test case, here is what i made :

dd if=/dev/urandom of=begin.iso bs=1M count=100
dd if=/dev/urandom of=end.iso bs=1M count=300

dd if=/dev/urandom of=middle1.iso bs=1M count=50
dd if=/dev/urandom of=middle2.iso bs=1M count=50


Lets build our two files :
cat begin.iso middle1.iso end.iso >file1.iso
cat begin.iso middle2.iso end.iso >file2.iso

So we end up with two files of identical size, but 50MB diff somewhere 
inside :
-rw-r--r-- 1 kuri users 471859200  2 févr. 14:55 file1.iso
-rw-r--r-- 1 kuri users 471859200  2 févr. 14:55 file2.iso

I now encrypt them with rsyncrypto :
rsyncrypto --gzip=nullgzip file1.iso{,.enc} backup.{keys,crt}
rsyncrypto --gzip=nullgzip file2.iso{,.enc} backup.{keys,crt}

The first noticeable thing i see is that they dont do the same size once 
encrypted :
-rw-r--r-- 1 root root  472063316  2 févr. 14:55 file1.iso.enc
-rw-r--r-- 1 root root  472062484  2 févr. 14:55 file2.iso.enc

Now if i copy the original files using rsync, I get interesting i/o work 
:
[kuri:~/tmp/random] $ rsync --progress -av --inplace --no-whole-file -i 
file1.iso test/file.iso
sending incremental file list
> f+++++++++ file1.iso
     471,859,200 100%  208.71MB/s    0:00:02 (xfr#1, to-chk=0/1)

sent 471,974,500 bytes  received 35 bytes  188,789,814.00 bytes/sec
total size is 471,859,200  speedup is 1.00
[kuri:~/tmp/random] $ rsync --progress -av --inplace --no-whole-file -i 
file2.iso test/file.iso
sending incremental file list
> f..t...... file2.iso
     471,859,200 100%  135.90MB/s    0:00:03 (xfr#1, to-chk=0/1)

sent 52,543,948 bytes  received 152,118 bytes  8,107,087.08 bytes/sec
total size is 471,859,200  speedup is 8.95
[kuri:~/tmp/random] $


Now i copy the encrypted files :
[kuri:~/tmp/random] $ rsync --progress -av --inplace --no-whole-file -i 
file1.iso.enc test/file.iso.enc
sending incremental file list
> f+++++++++ file1.iso.enc
     472,063,316 100%  180.86MB/s    0:00:02 (xfr#1, to-chk=0/1)

sent 472,178,659 bytes  received 35 bytes  134,908,198.29 bytes/sec
total size is 472,063,316  speedup is 1.00
[kuri:~/tmp/random] $ rsync --progress -av --inplace --no-whole-file -i 
file2.iso.enc test/file.iso.enc
sending incremental file list
> f.st...... file2.iso.enc
     472,062,484 100%  111.87MB/s    0:00:04 (xfr#1, to-chk=0/1)

sent 52,608,319 bytes  received 152,188 bytes  9,592,819.45 bytes/sec
total size is 472,062,484  speedup is 8.95

So, it worked perfectly on this test, but sometimes,
it fails to do proper diff, so lets make another test file :
dd if=/dev/urandom of=middle3.iso bs=1M count=50
cat begin.iso middle3.iso end.iso >file3.iso
rsyncrypto --gzip=nullgzip file3.iso{,.enc} backup.{keys,crt}

Lets look at the files :
-rw-r--r-- 1 kuri users 471859200  2 févr. 14:55 file1.iso
-rw-r--r-- 1 kuri users 471859200  2 févr. 14:55 file2.iso
-rw-r--r-- 1 kuri users 471859200  3 févr. 09:07 file3.iso

-rw-r--r-- 1 root root 472063316  2 févr. 14:55 file1.iso.enc
-rw-r--r-- 1 root root 472062484  2 févr. 14:55 file2.iso.enc
-rw-r--r-- 1 root root 472062932  3 févr. 09:07 file3.iso.enc

Lets rsync the third file :
[kuri:~/tmp/random] $ rsync --progress -av --inplace --no-whole-file -i 
file3.iso.enc test/file.iso.enc
sending incremental file list
> f.st...... file3.iso.enc
     472,062,932 100%   53.22MB/s    0:00:08 (xfr#1, to-chk=0/1)

sent 367,307,827 bytes  received 152,188 bytes  34,996,191.90 bytes/sec
total size is 472,062,932  speedup is 1.28

So, it copied 350MB of a 450MB file that only had 50MB changed.
Lets see with the unencrypted files :
[kuri:~/tmp/random] $ rsync --progress -av --inplace --no-whole-file -i 
file3.iso test/file.iso
sending incremental file list
> f..t...... file3.iso
     471,859,200 100%  135.29MB/s    0:00:03 (xfr#1, to-chk=0/1)

sent 52,543,947 bytes  received 152,118 bytes  9,581,102.73 bytes/sec
total size is 471,859,200  speedup is 8.95

So it is working properlly if files are not encrypted.
Is it possible that due to having different filesize, rsync algorithm 
fails ?
Do you have any hints ?
The only thing i can see is that between file1.iso.enc and 
file2.iso.enc,
the filesize dropped a little, and between file2.iso.enc and 
file3.iso.enc it is higher,
but i have no idea if this can be related...

Checking at the data of each encrypted file i can see that the last 
300MB are exactly the same :
[kuri:~/tmp/random] $ tail -c 314572800 file1.iso.enc | sha1sum
ee0c8bb19a620f7cdd44705b1293df461af389bc  -
[kuri:~/tmp/random] $ tail -c 314572800 file2.iso.enc | sha1sum
ee0c8bb19a620f7cdd44705b1293df461af389bc  -
[kuri:~/tmp/random] $ tail -c 314572800 file3.iso.enc | sha1sum
ee0c8bb19a620f7cdd44705b1293df461af389bc  -

But the first 100MB are not :
[kuri:~/tmp/random] $ head -c 104857600 file1.iso.enc | sha1sum
d86fa953b25e1a01a53409f567cc845535525dc1  -
[kuri:~/tmp/random] $ head -c 104857600 file2.iso.enc | sha1sum
0c10309cf8fe0bb349b05081c782469e4c2fb0e2  -
[kuri:~/tmp/random] $ head -c 104857600 file3.iso.enc | sha1sum
338ba6c1a58dde8c334092986e5ce20e3b8114df  -


Any help would be greatly appreciated, i would like to backup even 
bigger files (some GBs), where over 90% of the file gets transferred if 
encrypted with rsyncrypto while only 2-4MB would be transferred 
otherwise.

rsyncrypto with --backup-dir like in rsync

[Zurd <zurd33@gm...>]

The original rsync has an option --backup that works with --backup-dir.
When they are used, all the modified and/or deleted files are put in the
--backup-dir argument.

When using the --delete option at the same time, the destination folder is
then always kept as a perfect copy like the source folder. And the
--backup-dir folder has all the modified/deleted files in it.

An example of that command would be:
rsync --archive --delete --backup
--backup-dir=/home/user/backup-2014-12-30/  /home/user/backup-source/
/home/user/backup-destination/

Does rsyncrypto has an option like that?


Cheers,

Re: rsyncrypto crashing

[Frederico Rodrigues Abraham <devotion97@gm...>]

I'm sure.. I even put a print together with changed lines, it appears
normally.

Here is 'diff' between the original source and the patched file in my
directory:

[bacon:/local2/users/fabraham/pessoal/backup/rsyncryptodebug/rsyncrypto-1.12]
diff autommap.h ../rsyncrypto-1.12.patched/autommap.h
33c33
<     autommap() : ptr(reinterpret_cast<void *>(-1)), size(0)
---
>     autommap() : ptr(reinterpret_cast<void *>(-1l)), size(0)
39c39
<         if( ptr==reinterpret_cast<void *>(-1) ) {
---
>         if( ptr==reinterpret_cast<void *>(-1l) ) {
47c47
<     autommap(file_t fd, int prot) : ptr(reinterpret_cast<void *>(-1)),
size(0)
---
>     autommap(file_t fd, int prot) : ptr(reinterpret_cast<void *>(-1l)),
size(0)
79c79
<         that.ptr=reinterpret_cast<void *>(-1);
---
>         that.ptr=reinterpret_cast<void *>(-1l);
86c86
<         if( ptr!=reinterpret_cast<void *>(-1) ) {
---
>         if( ptr!=reinterpret_cast<void *>(-1l) ) {
89c89
<         ptr=reinterpret_cast<void *>(-1);
---
>         ptr=reinterpret_cast<void *>(-1l);




On Fri, Mar 28, 2014 at 9:46 AM, Shachar Shemesh <shachar@...>wrote:

>  On 22/03/14 14:12, Frederico Rodrigues Abraham wrote:
>
> I patched the source, didn't seem to make a difference:
>
> I'm not sure how to continue from here. The source says there is no way
> for that value to reach that point in the code. I'll try to come up with a
> version with debug logs and see if that helps.
>
> In the mean while, are you sure you ran the version compiled with the
> patch?
>
> Thanks,
> Shachar
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Rsyncrypto-devel mailing list
> Rsyncrypto-devel@...
> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>
>


-- 
    -- Fred

Re: rsyncrypto crashing

[Shachar Shemesh <shachar@sh...>]

On 22/03/14 14:12, Frederico Rodrigues Abraham wrote:
> I patched the source, didn't seem to make a difference:
I'm not sure how to continue from here. The source says there is no way
for that value to reach that point in the code. I'll try to come up with
a version with debug logs and see if that helps.

In the mean while, are you sure you ran the version compiled with the patch?

Thanks,
Shachar

Re: rsyncrypto crashing

[Frederico Rodrigues Abraham <devotion97@gm...>]

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">I patched the source, didn't seem to
      make a difference:<br>
      <br>
      Program received signal SIGSEGV, Segmentation fault.<br>
      key::read_key (buffer=buffer@...=0xffffffffffffffff &lt;Address
      0xffffffffffffffff out of bounds&gt;) at crypt_key.cpp:44<br>
      44          if( buff-&gt;version!=htonl(VERSION_MAGIC_1) )<br>
      (gdb) bt<br>
      #0  key::read_key (buffer=buffer@...=0xffffffffffffffff
      &lt;Address 0xffffffffffffffff out of bounds&gt;) at
      crypt_key.cpp:44<br>
      #1  0x00000000004047f0 in read_header (headfd=...) at
      crypto.cpp:102<br>
      #2  0x0000000000408a3a in file_decrypt (src_file=0x9357158
      "filesencrypted/files/40AEBACBA5170D57464965CA52861A2F", <br>
          dst_file=0x9357238
      "../ugah/files/work/tecgraf/lib/visnew/include/old/sg/strat/render/slrender.h",
      key_file=0x93572d8
      "filesencrypted/keys/files/40AEBACBA5170D57464965CA52861A2F", <br>
          rsa_key=rsa_key@...=0x6296a0,
      stat=stat@...=0x7fffffffb660) at file.cpp:445<br>
      #3  0x0000000000409b80 in recurse_dir_enc
      (src_dir=src_dir@...=0x7fffffffc588 "filesencrypted/files",
      dst_dir=dst_dir@...=0x7fffffffc59d "..",
      key_dir=key_dir@...=0x7fffffffc5a0 "filesencrypted/keys", <br>
          rsa_key=rsa_key@...=0x6296a0, op=op@...=0x408990
      &lt;file_decrypt(char const*, char const*, char const*, rsa_st*,
      stat const*)&gt;, src_offset=src_offset@...=15,
      op_handle_dir=op_handle_dir@...=false, <br>
          opname=opname@...=0x410569 "Decrypting",
      dstname=dstname@...=0x40c4f0 &lt;filemap::namecat_decrypt(char
      const*, char const*, unsigned int)&gt;, <br>
          keyname=keyname@...=0x409520 &lt;name_concat(char const*,
      char const*, unsigned int)&gt;) at file.cpp:207<br>
      #4  0x000000000040a315 in dir_encrypt (src_dir=0x7fffffffc588
      "filesencrypted/files", dst_dir=0x7fffffffc59d "..",
      key_dir=0x7fffffffc5a0 "filesencrypted/keys",
      rsa_key=rsa_key@...=0x6296a0, <br>
          op=op@...=0x408990 &lt;file_decrypt(char const*, char
      const*, char const*, rsa_st*, stat const*)&gt;,
      opname=opname@...=0x410569 "Decrypting", <br>
          dstname=dstname@...=0x40c4f0
      &lt;filemap::namecat_decrypt(char const*, char const*, unsigned
      int)&gt;, keyname=keyname@...=0x409520 &lt;name_concat(char
      const*, char const*, unsigned int)&gt;) at file.cpp:323<br>
      #5  0x00000000004030f9 in main (argc=&lt;optimized out&gt;,
      argv=&lt;optimized out&gt;) at main.cpp:170<br>
      (gdb) <br>
      <br>
      -- Fred<br>
      <br>
      On 18-03-2014 12:07, Shachar Shemesh wrote:<br>
    </div>
    <blockquote cite="mid:5328614C.1030405@..." type="cite">
      <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
      <style type="text/css">body p { margin-bottom: 0.2cm; margin-top: 0pt; } </style>
      <div class="moz-cite-prefix">On 18/03/14 13:55, Frederico
        Rodrigues Abraham wrote:<br>
      </div>
      <blockquote
cite="mid:CAPx=+Sbs5x0ro5am_Ho8CDyvDqtHHc9r3FS5Ns4N6heEqRc42Q@..."
        type="cite">
        <div dir="ltr">Here is the stack trace:<br>
        </div>
      </blockquote>
      While we're at it, and in addition to the strace output, please
      try applying the attached patch. It should solve the actual crash,
      but I suspect rsyncrypto will still fail (just more gracefully).<br>
      <br>
      Just cd to the source directory, run "patch -p0 &lt;
      /tmp/crash.patch", and then run "make" again. Let me know whether
      it solves the crash.<br>
      <br>
      Shachar<br>
    </blockquote>
    <br>
  </body>
</html>

Re: rsyncrypto crashing

[Shachar Shemesh <shachar@sh...>]

On 21/03/14 13:43, Frederico Rodrigues Abraham wrote:
> It's still crashing after the patch. I'll run with gdb tonight to give
> you the stack trace.
>
Please reply with all non-private correspondences to the list.

Rsyncrypto is an open source project. Whenever you reply to me in
private, you are denying others, who might be having the same problems,
the benefit of the archive and google. This means that it falls squarely
on me to personally handle each and every such problem. I find it unfair
to me.

As such, please respect my request that, barring a really good reason
(such as sending a huge trace file with sensitive information), all
support for rsyncrypto go through the mailing list.

Thank you,
Shachar

Re: rsyncrypto crashing

[Shachar Shemesh <shachar@sh...>]

On 18/03/14 13:55, Frederico Rodrigues Abraham wrote:
> Here is the stack trace:
While we're at it, and in addition to the strace output, please try
applying the attached patch. It should solve the actual crash, but I
suspect rsyncrypto will still fail (just more gracefully).

Just cd to the source directory, run "patch -p0 < /tmp/crash.patch", and
then run "make" again. Let me know whether it solves the crash.

Shachar

Re: rsyncrypto crashing

[Shachar Shemesh <shachar@sh...>]

On 18/03/14 13:55, Frederico Rodrigues Abraham wrote:
> Here is the stack trace:
>
> Program received signal SIGSEGV, Segmentation fault.
> key::read_key (buffer=buffer@...=0xffffffffffffffff <Address
> 0xffffffffffffffff out of bounds>) at crypt_key.cpp:44
> 44          if( buff->version!=htonl(VERSION_MAGIC_1) )
> (gdb)
> (gdb) bt
> #0  key::read_key (buffer=buffer@...=0xffffffffffffffff <Address
> 0xffffffffffffffff out of bounds>) at crypt_key.cpp:44
> #1  0x00000000004047f0 in read_header (headfd=...) at crypto.cpp:102
> #2  0x0000000000408a3a in file_decrypt (src_file=0x9357158
> "filesencrypted/files/40AEBACBA5170D57464965CA52861A2F",
>     dst_file=0x9357238
> "../ugah/files/work/tecgraf/lib/visnew/include/old/sg/strat/render/slrender.h",
> key_file=0x93572d8
> "filesencrypted/keys/files/40AEBACBA5170D57464965CA52861A2F",
>     rsa_key=rsa_key@...=0x6296a0, stat=stat@...=0x7fffffffb660) at
> file.cpp:445
This makes zero sense.

The segmentation fault is due to trying to dereference a pointer
pointing to 0xffffffffffffffff (-1), which is what mmap returns when it
fails. This, like I said, makes no sense, as in such a case it should
have thrown an exception (hmmm...., upon looking at the code again,
maybe not...).

Can you please run the code with strace and send me (in private) the
result? I can see why the error wouldn't be detected on 64 bit, but I
still don't understand why mmap would fail to begin with.

Thanks,
Shachar

Re: rsyncrypto crashing

[Frederico Rodrigues Abraham <devotion97@gm...>]

Here is the stack trace:

Program received signal SIGSEGV, Segmentation fault.
key::read_key (buffer=buffer@...=0xffffffffffffffff <Address
0xffffffffffffffff out of bounds>) at crypt_key.cpp:44
44          if( buff->version!=htonl(VERSION_MAGIC_1) )
(gdb)
(gdb) bt
#0  key::read_key (buffer=buffer@...=0xffffffffffffffff <Address
0xffffffffffffffff out of bounds>) at crypt_key.cpp:44
#1  0x00000000004047f0 in read_header (headfd=...) at crypto.cpp:102
#2  0x0000000000408a3a in file_decrypt (src_file=0x9357158
"filesencrypted/files/40AEBACBA5170D57464965CA52861A2F",
    dst_file=0x9357238
"../ugah/files/work/tecgraf/lib/visnew/include/old/sg/strat/render/slrender.h",
key_file=0x93572d8
"filesencrypted/keys/files/40AEBACBA5170D57464965CA52861A2F",
    rsa_key=rsa_key@...=0x6296a0, stat=stat@...=0x7fffffffb660) at
file.cpp:445
#3  0x0000000000409b80 in recurse_dir_enc (src_dir=src_dir@...=0x7fffffffc588
"filesencrypted/files", dst_dir=dst_dir@...=0x7fffffffc59d "..",
    key_dir=key_dir@...=0x7fffffffc5a0 "filesencrypted/keys",
rsa_key=rsa_key@...=0x6296a0, op=op@...=0x408990 <file_decrypt(char
const*, char const*, char const*, rsa_st*, stat const*)>,
    src_offset=src_offset@...=15, op_handle_dir=op_handle_dir@...=false,
opname=opname@...=0x410569 "Decrypting", dstname=dstname@...=
    0x40c4f0 <filemap::namecat_decrypt(char const*, char const*, unsigned
int)>, keyname=keyname@...=0x409520 <name_concat(char const*, char
const*, unsigned int)>) at file.cpp:207
#4  0x000000000040a315 in dir_encrypt (src_dir=0x7fffffffc588
"filesencrypted/files", dst_dir=0x7fffffffc59d "..", key_dir=0x7fffffffc5a0
"filesencrypted/keys", rsa_key=rsa_key@...=0x6296a0,
    op=op@...=0x408990 <file_decrypt(char const*, char const*, char
const*, rsa_st*, stat const*)>, opname=opname@...=0x410569 "Decrypting",
    dstname=dstname@...=0x40c4f0 <filemap::namecat_decrypt(char const*,
char const*, unsigned int)>, keyname=keyname@...=0x409520
<name_concat(char const*, char const*, unsigned int)>) at file.cpp:323
#5  0x00000000004030f9 in main (argc=<optimized out>, argv=<optimized out>)
at main.cpp:170
(gdb)



On Sun, Mar 16, 2014 at 11:04 AM, Frederico Rodrigues Abraham <
devotion97@...> wrote:

> It's saying 'not stripped', cool. Running it.
>
> It's 64 bit intel.
>
> -- Fred
>
>
> On Sun, Mar 16, 2014 at 11:03 AM, Shachar Shemesh <shachar@...>wrote:
>
>>  On 16/03/14 15:49, Frederico Rodrigues Abraham wrote:
>>
>> ok, ./configure && make worked. but is the executable with debug info? no
>> special flags for 'make' ?
>>
>> "file rsyncrypto"
>>
>> It should say it is "not stripped".
>>
>> Also, what platform is this? Is it 64bit Intel?
>>
>> Shachar
>>
>>
>>
>> On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <shachar@...>wrote:
>>
>>>  On 16/03/14 15:19, Frederico Rodrigues Abraham wrote:
>>>
>>>
>>> Any ideas?
>>>
>>> Yes. Try to build with the standard "./configure ; make" idiom.
>>> Obviously, the packaging for this has rotted to the point it no longer
>>> compiles :-(
>>>
>>> I'll get around, sometimes, to update the Debian package. The Ubuntu
>>> package, however, is out of my hands. It will get updated on its own or
>>> not. At least on Debian, however, the package complains a lot, but still
>>> compiles.
>>>
>>> I'm not sure whether to tell you to open a bug on the Ubuntu package,
>>> but the manual compile should at least tell us where the problem is.
>>>
>>> Shachar
>>>
>>> Thanks,
>>> -- Fred
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Learn Graph Databases - Download FREE O'Reilly Book
>>> "Graph Databases" is the definitive new guide to graph databases and their
>>> applications. Written by three acclaimed leaders in the field,
>>> this first edition is now available. Download your free book today!http://p.sf.net/sfu/13534_NeoTech
>>>
>>>
>>>
>>> _______________________________________________
>>> Rsyncrypto-devel mailing listRsyncrypto-devel@...nethttps://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>>>
>>>
>>>
>>
>>
>> --
>>     -- Fred
>>
>>
>>
>
>
> --
>     -- Fred
>



-- 
    -- Fred

Re: rsyncrypto crashing

[Frederico Rodrigues Abraham <devotion97@gm...>]

It's saying 'not stripped', cool. Running it.

It's 64 bit intel.

-- Fred


On Sun, Mar 16, 2014 at 11:03 AM, Shachar Shemesh <shachar@...>wrote:

>  On 16/03/14 15:49, Frederico Rodrigues Abraham wrote:
>
> ok, ./configure && make worked. but is the executable with debug info? no
> special flags for 'make' ?
>
> "file rsyncrypto"
>
> It should say it is "not stripped".
>
> Also, what platform is this? Is it 64bit Intel?
>
> Shachar
>
>
>
> On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <shachar@...>wrote:
>
>>  On 16/03/14 15:19, Frederico Rodrigues Abraham wrote:
>>
>>
>> Any ideas?
>>
>> Yes. Try to build with the standard "./configure ; make" idiom.
>> Obviously, the packaging for this has rotted to the point it no longer
>> compiles :-(
>>
>> I'll get around, sometimes, to update the Debian package. The Ubuntu
>> package, however, is out of my hands. It will get updated on its own or
>> not. At least on Debian, however, the package complains a lot, but still
>> compiles.
>>
>> I'm not sure whether to tell you to open a bug on the Ubuntu package, but
>> the manual compile should at least tell us where the problem is.
>>
>> Shachar
>>
>> Thanks,
>> -- Fred
>>
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!http://p.sf.net/sfu/13534_NeoTech
>>
>>
>>
>> _______________________________________________
>> Rsyncrypto-devel mailing listRsyncrypto-devel@...nethttps://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>>
>>
>>
>
>
> --
>     -- Fred
>
>
>


-- 
    -- Fred

Re: rsyncrypto crashing

[Shachar Shemesh <shachar@sh...>]

On 16/03/14 15:49, Frederico Rodrigues Abraham wrote:
> ok, ./configure && make worked. but is the executable with debug info?
> no special flags for 'make' ?
"file rsyncrypto"

It should say it is "not stripped".

Also, what platform is this? Is it 64bit Intel?

Shachar
>
>
> On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <shachar@...
> <mailto:shachar@...>> wrote:
>
>     On 16/03/14 15:19, Frederico Rodrigues Abraham wrote:
>>
>>     Any ideas?
>     Yes. Try to build with the standard "./configure ; make" idiom.
>     Obviously, the packaging for this has rotted to the point it no
>     longer compiles :-(
>
>     I'll get around, sometimes, to update the Debian package. The
>     Ubuntu package, however, is out of my hands. It will get updated
>     on its own or not. At least on Debian, however, the package
>     complains a lot, but still compiles.
>
>     I'm not sure whether to tell you to open a bug on the Ubuntu
>     package, but the manual compile should at least tell us where the
>     problem is.
>
>     Shachar
>>     Thanks,
>>     -- Fred
>>
>>
>>     ------------------------------------------------------------------------------
>>     Learn Graph Databases - Download FREE O'Reilly Book
>>     "Graph Databases" is the definitive new guide to graph databases and their
>>     applications. Written by three acclaimed leaders in the field,
>>     this first edition is now available. Download your free book today!
>>     http://p.sf.net/sfu/13534_NeoTech
>>
>>
>>     _______________________________________________
>>     Rsyncrypto-devel mailing list
>>     Rsyncrypto-devel@... <mailto:Rsyncrypto-devel@...>
>>     https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>
>
>
>
> -- 
>     -- Fred

Re: rsyncrypto crashing

[Frederico Rodrigues Abraham <devotion97@gm...>]

ok, ./configure && make worked. but is the executable with debug info? no
special flags for 'make' ?


On Sun, Mar 16, 2014 at 10:35 AM, Shachar Shemesh <shachar@...>wrote:

>  On 16/03/14 15:19, Frederico Rodrigues Abraham wrote:
>
>
> Any ideas?
>
> Yes. Try to build with the standard "./configure ; make" idiom. Obviously,
> the packaging for this has rotted to the point it no longer compiles :-(
>
> I'll get around, sometimes, to update the Debian package. The Ubuntu
> package, however, is out of my hands. It will get updated on its own or
> not. At least on Debian, however, the package complains a lot, but still
> compiles.
>
> I'm not sure whether to tell you to open a bug on the Ubuntu package, but
> the manual compile should at least tell us where the problem is.
>
> Shachar
>
> Thanks,
> -- Fred
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!http://p.sf.net/sfu/13534_NeoTech
>
>
>
> _______________________________________________
> Rsyncrypto-devel mailing listRsyncrypto-devel@...nethttps://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>
>
>


-- 
    -- Fred

Re: rsyncrypto crashing

[Shachar Shemesh <shachar@sh...>]

On 16/03/14 15:19, Frederico Rodrigues Abraham wrote:
>
> Any ideas?
Yes. Try to build with the standard "./configure ; make" idiom.
Obviously, the packaging for this has rotted to the point it no longer
compiles :-(

I'll get around, sometimes, to update the Debian package. The Ubuntu
package, however, is out of my hands. It will get updated on its own or
not. At least on Debian, however, the package complains a lot, but still
compiles.

I'm not sure whether to tell you to open a bug on the Ubuntu package,
but the manual compile should at least tell us where the problem is.

Shachar
> Thanks,
> -- Fred
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
>
>
> _______________________________________________
> Rsyncrypto-devel mailing list
> Rsyncrypto-devel@...
> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel

Re: rsyncrypto crashing

[Frederico Rodrigues Abraham <devotion97@gm...>]

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 16-03-2014 00:18, Shachar Shemesh
      wrote:<br>
    </div>
    <blockquote cite="mid:53251807.3000409@..." type="cite">
      <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
      <style type="text/css">body p { margin-bottom: 0.2cm; margin-top: 0pt; } </style>
      <div class="moz-cite-prefix">Hello Frederico,<br>
        <br>
        On 16/03/14 00:48, Frederico Rodrigues Abraham wrote:<br>
      </div>
      <blockquote cite="mid:5324D8AE.9050408@..." type="cite">
        <pre wrap="">Hi all.
My rsyncrypto started crashing ... I'm decrypting directories with 
filename encryption.</pre>
      </blockquote>
      By "started crashing", I'm assuming you mean it did work before.
      Can you say what changed?<br>
      <br>
      Let's start with some background material. What version of
      rsyncrypto are you using (run rsyncrypto --version)? Is it the
      standard one provided by the distribution? What command line are
      you using? (it is okay to fudge the directory names, if those are
      sensitive). What is the precise error message?<br>
    </blockquote>
    <br>
    It's the standard provided with the distribution, version 1.12. It
    worked before normally, now I'm getting this:<br>
    <br>
    Decrypting filesencrypted/files/40AEBACBA5170D57464965CA52861A2F<br>
    Segmentation fault (core dumped)<br>
    <br>
    Command line is:<br>
    <br>
      rsyncrypto -vvvvv -n .ssh/filemap --delete --delete-keys -d -r
    filesencrypted/files .. filesencrypted/keys .ssh/backup.key<br>
    <br>
    (I just added the -vvvvv to try to debug, but no success. Crashes
    without it)<br>
    <br>
    <blockquote cite="mid:53251807.3000409@..." type="cite">
      <blockquote cite="mid:5324D8AE.9050408@..." type="cite">
        <pre wrap="">
Is it possible for someone to help me investigating this? Without the 
need for me to send the actual data?</pre>
      </blockquote>
      I can certainly try.<br>
      <blockquote cite="mid:5324D8AE.9050408@..." type="cite">
        <pre wrap="">An executable with debugging information maybe? I'm running on Ubuntu 
Linux 13.10.</pre>
      </blockquote>
      Perform the following tasks to build one (assuming you are running
      the distribution's binary):<br>
      create a clean directory and cd to it<br>
      sudo apt-get build-dep rsyncrypto<br>
      apt-get source rsyncrypto<br>
      cd rsyncrypto-&lt;version&gt;<br>
      dpkg-buildpackage<br>
      <br>
      your work directory should have a non-stripped (i.e. - with debug
      info) version of the file. Use it. Make sure to run "ulimit -c
      unlimited" first. After crash, a file called "core" should be
      created. Run "gdb &lt;path to&gt;/rsyncrypto core", type "bt", and
      paste the output here. This will provide a backtrace of the point
      of the crash.<br>
    </blockquote>
    <br>
    I got an error. After the commands:<br>
    <br>
       130  9:38    mkdir rsyncryptodebug<br>
       131  9:38    cd rsyncryptodebug<br>
       132  9:38    sudo apt-get build-dep rsyncrypto<br>
       133  9:39    apt-get source rsyncrypto<br>
       134  9:40    cd rsyncrypto-1.12/<br>
       135  9:40    dpkg-buildpackage<br>
    <br>
    [bacon:/local2/users/fabraham/pessoal/backup/rsyncryptodebug/rsyncrypto-1.12]

    dpkg-buildpackage<br>
    dpkg-buildpackage: source package rsyncrypto<br>
    dpkg-buildpackage: source version 1.12-1build1<br>
    dpkg-buildpackage: source changed by Colin Watson <a
      class="moz-txt-link-rfc2396E" href="mailto:cjwatson@...">&lt;cjwatson@...&gt;</a><br>
    dpkg-buildpackage: host architecture amd64<br>
     dpkg-source --before-build rsyncrypto-1.12<br>
     fakeroot debian/rules clean<br>
    dh_testdir<br>
    dh_testroot<br>
    rm -f build-stamp<br>
    [ ! -f Makefile ] || /usr/bin/make distclean<br>
    dh_clean<br>
    dh_clean: Compatibility levels before 5 are deprecated (level 4 in
    use)<br>
     dpkg-source -b rsyncrypto-1.12<br>
    dpkg-source: warning: no source format specified in
    debian/source/format, see dpkg-source(1)<br>
    dpkg-source: info: using source format `1.0'<br>
    dpkg-source: info: building rsyncrypto using existing
    rsyncrypto_1.12.orig.tar.gz<br>
    dpkg-source: info: building rsyncrypto in
    rsyncrypto_1.12-1build1.diff.gz<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto_1.12-1build1.diff.gz: binary file
    contents changed<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto_1.12.orig.tar.gz: binary file contents
    changed<br>
    dpkg-source: warning: file
    rsyncrypto-1.12/rsyncrypto-1.12/COPYING.rtf has no final newline
    (either original or modified version)<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/install-sh' will not be represented in diff<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/depcomp' will not be represented in diff<br>
    dpkg-source: warning: file
    rsyncrypto-1.12/rsyncrypto-1.12/INSTALL.win has no final newline
    (either original or modified version)<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/bootstrap' will not be represented in diff<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/configure' will not be represented in diff<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/missing' will not be represented in diff<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/debian/rules' will not be represented in diff<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg1.key: binary file contents
    changed<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg1.enc: binary file contents
    changed<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg2.key: binary file contents
    changed<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg3: binary file contents
    changed<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg1: binary file contents
    changed<br>
    dpkg-source: warning: newly created empty file
    'rsyncrypto-1.12/tests/reg2.rot' will not be represented in diff<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg3.enc: binary file contents
    changed<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/tests/testcrypt' will not be represented in diff<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/tests/nullgzip' will not be represented in diff<br>
    dpkg-source: warning: newly created empty file
    'rsyncrypto-1.12/tests/reg1.rot' will not be represented in diff<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg2.enc: binary file contents
    changed<br>
    dpkg-source: warning: executable mode 0755 of
    'rsyncrypto-1.12/tests/regtest' will not be represented in diff<br>
    dpkg-source: warning: file
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg2 has no final newline
    (either original or modified version)<br>
    dpkg-source: error: cannot represent change to
    rsyncrypto-1.12/rsyncrypto-1.12/tests/reg3.key: binary file contents
    changed<br>
    dpkg-source: warning: file
    rsyncrypto-1.12/rsyncrypto-1.12/win32/nullgzip.cpp has no final
    newline (either original or modified version)<br>
    dpkg-source: warning: file
    rsyncrypto-1.12/rsyncrypto-1.12/win32/types.h has no final newline
    (either original or modified version)<br>
    dpkg-source: warning: file
    rsyncrypto-1.12/rsyncrypto-1.12/win32/win32redir.h has no final
    newline (either original or modified version)<br>
    dpkg-source: warning: the diff modifies the following upstream
    files:<br>
     config.guess<br>
     config.sub<br>
     rsyncrypto-1.12/AUTHORS<br>
     rsyncrypto-1.12/COPYING<br>
     rsyncrypto-1.12/COPYING.rtf<br>
     rsyncrypto-1.12/ChangeLog<br>
     rsyncrypto-1.12/INSTALL<br>
     rsyncrypto-1.12/INSTALL.win<br>
     rsyncrypto-1.12/Makefile.am<br>
     rsyncrypto-1.12/Makefile.in<br>
     rsyncrypto-1.12/NEWS<br>
     rsyncrypto-1.12/README<br>
     rsyncrypto-1.12/aclocal.m4<br>
     rsyncrypto-1.12/aes_crypt.cpp<br>
     rsyncrypto-1.12/aes_crypt.h<br>
     rsyncrypto-1.12/autoarray.h<br>
     rsyncrypto-1.12/autodir.h<br>
     rsyncrypto-1.12/autofd.h<br>
     rsyncrypto-1.12/autommap.h<br>
     rsyncrypto-1.12/autopipe.h<br>
     rsyncrypto-1.12/blocksizes.cpp<br>
     rsyncrypto-1.12/bootstrap<br>
     rsyncrypto-1.12/bufferfd.cpp<br>
     rsyncrypto-1.12/bufferfd.h<br>
     rsyncrypto-1.12/config.guess<br>
     rsyncrypto-1.12/config.h.in<br>
     rsyncrypto-1.12/config.sub<br>
     rsyncrypto-1.12/configure<br>
     rsyncrypto-1.12/configure.ac<br>
     rsyncrypto-1.12/contrib/argtable2.vcproj<br>
     rsyncrypto-1.12/contrib/gzip-rsyncable.diff<br>
     rsyncrypto-1.12/crypt_key.cpp<br>
     rsyncrypto-1.12/crypt_key.h<br>
     rsyncrypto-1.12/crypto.cpp<br>
     rsyncrypto-1.12/crypto.h<br>
     rsyncrypto-1.12/debian/README.Debian<br>
     rsyncrypto-1.12/debian/changelog<br>
     rsyncrypto-1.12/debian/compat<br>
     rsyncrypto-1.12/debian/control<br>
     rsyncrypto-1.12/debian/copyright<br>
     rsyncrypto-1.12/debian/dirs<br>
     rsyncrypto-1.12/debian/docs<br>
     rsyncrypto-1.12/debian/rsyncrypto.examples<br>
     rsyncrypto-1.12/debian/rules<br>
     rsyncrypto-1.12/debian/watch<br>
     rsyncrypto-1.12/depcomp<br>
     rsyncrypto-1.12/docs/filelist.txt<br>
     rsyncrypto-1.12/docs/rsyncrypto.html<br>
     rsyncrypto-1.12/docs/rsyncrypto_recover.html<br>
     rsyncrypto-1.12/file.cpp<br>
     rsyncrypto-1.12/file.h<br>
     rsyncrypto-1.12/filemap.cpp<br>
     rsyncrypto-1.12/filemap.h<br>
     rsyncrypto-1.12/install-sh<br>
     rsyncrypto-1.12/main.cpp<br>
     rsyncrypto-1.12/missing<br>
     rsyncrypto-1.12/precomp.h<br>
     rsyncrypto-1.12/process.cpp<br>
     rsyncrypto-1.12/process.h<br>
     rsyncrypto-1.12/random.h<br>
     rsyncrypto-1.12/rcserror.h<br>
     rsyncrypto-1.12/recover.cpp<br>
     rsyncrypto-1.12/redir.cpp<br>
     rsyncrypto-1.12/redir.h<br>
     rsyncrypto-1.12/release.checklist<br>
     rsyncrypto-1.12/rsyncrypto.h<br>
     rsyncrypto-1.12/rsyncrypto.man<br>
     rsyncrypto-1.12/rsyncrypto.sln<br>
     rsyncrypto-1.12/rsyncrypto.vcproj<br>
     rsyncrypto-1.12/rsyncrypto_recover.man<br>
     rsyncrypto-1.12/rsyncrypto_recover.vcproj<br>
     rsyncrypto-1.12/tests/README<br>
     rsyncrypto-1.12/tests/cert.crt<br>
     rsyncrypto-1.12/tests/cert.key<br>
     rsyncrypto-1.12/tests/nullgzip<br>
     rsyncrypto-1.12/tests/reg2<br>
     rsyncrypto-1.12/tests/reg3.rot<br>
     rsyncrypto-1.12/tests/regtest<br>
     rsyncrypto-1.12/tests/regtestw32<br>
     rsyncrypto-1.12/tests/testcrypt<br>
     rsyncrypto-1.12/win32/Setup.vdproj<br>
     rsyncrypto-1.12/win32/autodir.h<br>
     rsyncrypto-1.12/win32/autofd.h<br>
     rsyncrypto-1.12/win32/autohandle.h<br>
     rsyncrypto-1.12/win32/autommap.h<br>
     rsyncrypto-1.12/win32/autopipe.h<br>
     rsyncrypto-1.12/win32/config.h<br>
     rsyncrypto-1.12/win32/nullgzip.cpp<br>
     rsyncrypto-1.12/win32/nullgzip.vcproj<br>
     rsyncrypto-1.12/win32/process.cpp<br>
     rsyncrypto-1.12/win32/process.h<br>
     rsyncrypto-1.12/win32/redir.cpp<br>
     rsyncrypto-1.12/win32/resource.h<br>
     rsyncrypto-1.12/win32/rsyncrypto.rc<br>
     rsyncrypto-1.12/win32/stdafx.cpp<br>
     rsyncrypto-1.12/win32/types.h<br>
     rsyncrypto-1.12/win32/win32glue.cpp<br>
     rsyncrypto-1.12/win32/win32redir.h<br>
     rsyncrypto_1.12-1build1.dsc<br>
    dpkg-source: info: use the '3.0 (quilt)' format to have separate and
    documented changes to upstream files, see dpkg-source(1)<br>
    dpkg-source: unrepresentable changes to source<br>
    dpkg-buildpackage: error: dpkg-source -b rsyncrypto-1.12 gave error
    exit status 1<br>
    <br>
    Any ideas?<br>
    Thanks,<br>
    -- Fred<br>
  </body>
</html>

Re: rsyncrypto crashing

[Shachar Shemesh <shachar@sh...>]

Hello Frederico,

On 16/03/14 00:48, Frederico Rodrigues Abraham wrote:
> Hi all.
> My rsyncrypto started crashing ... I'm decrypting directories with 
> filename encryption.
By "started crashing", I'm assuming you mean it did work before. Can you
say what changed?

Let's start with some background material. What version of rsyncrypto
are you using (run rsyncrypto --version)? Is it the standard one
provided by the distribution? What command line are you using? (it is
okay to fudge the directory names, if those are sensitive). What is the
precise error message?
>
> Is it possible for someone to help me investigating this? Without the 
> need for me to send the actual data?
I can certainly try.
> An executable with debugging information maybe? I'm running on Ubuntu 
> Linux 13.10.
Perform the following tasks to build one (assuming you are running the
distribution's binary):
create a clean directory and cd to it
sudo apt-get build-dep rsyncrypto
apt-get source rsyncrypto
cd rsyncrypto-<version>
dpkg-buildpackage

your work directory should have a non-stripped (i.e. - with debug info)
version of the file. Use it. Make sure to run "ulimit -c unlimited"
first. After crash, a file called "core" should be created. Run "gdb
<path to>/rsyncrypto core", type "bt", and paste the output here. This
will provide a backtrace of the point of the crash.

Hopefully, I can try and help you more after that.

Shachar

rsyncrypto crashing

[Frederico Rodrigues Abraham <devotion97@gm...>]

Hi all.
My rsyncrypto started crashing ... I'm decrypting directories with 
filename encryption.

Is it possible for someone to help me investigating this? Without the 
need for me to send the actual data?
An executable with debugging information maybe? I'm running on Ubuntu 
Linux 13.10.

Thanks,
-- Fred

filename translation not found

[Frederico Rodrigues Abraham <devotion97@gm...>]

"Filename translation not found(68110080386DA2B864AE4D5D74D9F90B): Success"

hello all.
i am using file name encryption and keep getting this message. when 
comparing the original data and decrypted data, some files also appear 
only among the decrypted data (files i have removed from the original data).

first question: is this because rsyncrypto was able to decrypt a file 
name even when it was not on the map file?

second question: the file (and key) exist in the encrypted directory but 
not on the contents of the file map. how come?

the command i'm using is:

rsyncrypto --modify-window 300 -v --delete --delete-keys -c -n 
/home/ugah/.ssh/filemap -r /home/ugah/files 
/home/ugah/filesencrypted/files /home/ugah/filesencrypted/keys 
/home/ugah/.ssh/backup.crt

thank you,
-- Fred

Re: Rsyncrypto messages

[Shachar Shemesh <shachar@sh...>]

On 11/29/2012 06:47 PM, chris.whatling@... wrote:
>
> Hi Shachar,
>
>  
>
> thanks for the quick response. You are correct, I can work with that,
> it's just that I'm running it from a threaded Delphi application that
> poles the command output pipe, so with and it not passing anything
> back I'm not detecting the exit.
>
>  
>
> I think I'll have to improve my monitoring of the pipe.
>
That is the preferred solution.

Another is to detect when rsyncrypto exits (the pipe is closed), and
then, if you do not see any errors, to assume everything is okay.

I will repeat, for the sake of emphasis, that the first option is the
recommended one.

Good luck,
Shachar

-- 
Shachar Shemesh

Re: Rsyncrypto messages

[Shachar Shemesh <shachar@sh...>]

On 11/28/2012 09:12 PM, Chris Whatling wrote:
> Hi, I'm trying to run Rsyncrypto followed by rsync in a sequence to encrypt 
> and then sync a number of files and folders.
>
> The problem I am having is that Rsyncrypto does not seem to output any message 
> or other text upon successful completion. It outputs 'Encrypting ..file .. etc 
> for each file, but nothing to indicate when it has finished the last one.
>
> I have tried increasing the verbosity with -v -v etc. which produces 
> additional output but nothing that indicates when it's done.
>
> Maybe I'm missing somthing obvious? 
Hi Chris,

I'm just throwing ideas around, here, but isn't the fact it exits with
return code zero indication enough that it completed successfully?

Shachar

-- 
Shachar Shemesh

Rsyncrypto messages

[Chris Whatling <chris.whatling@gm...>]

Hi, I'm trying to run Rsyncrypto followed by rsync in a sequence to encrypt 
and then sync a number of files and folders.

The problem I am having is that Rsyncrypto does not seem to output any message 
or other text upon successful completion. It outputs 'Encrypting ..file .. etc 
for each file, but nothing to indicate when it has finished the last one.

I have tried increasing the verbosity with -v -v etc. which produces 
additional output but nothing that indicates when it's done.

Maybe I'm missing somthing obvious? 

Any suggestions would be appreciated.

Thank. Regards Chris.

Re: Typo Report in Man Page - "fro stdin" and Question

[Shlomi Fish <shlomif@sh...>]

Hi Shachar,

On Thu, 21 Jun 2012 20:48:58 +0300
Shachar Shemesh <shachar@...> wrote:

> On 06/21/2012 06:06 PM, Shlomi Fish wrote:
> >> But despair not. You can achieve the equivalent level of security by
> >> encrypting your private key with a password, and storing it using the
> >> same provider you store your actual data. At this point in time
> >> rsyncrypto does not support decrypting from password protected RSA keys,
> >> but such support can be, fairly easily, added. Otherwise, in case of
> >> catastrophe, you can simply pull your encrypted key and decrypt is locally.
> >>
> > Thanks! I think that is also what Harold suggested.
> Same end result, give or take. Different mechanism.
> 
> RSA keys can be encrypted via a fairly standard fashion that has nothing
> to do with pgp or gpg. Openssl knows how to open such encrypted keys,
> and so will a future version of rsyncrypto.

I see - thanks for the clarification.

> >
> > BTW, do you think it would be possible to write an --rsyncable patch for xz
> > instead of gzip (see http://tukaani.org/xz/ ; http://en.wikipedia.org/wiki/Xz )
> I think you meant LZMA. 

Well, LZMA is the general algorithm while xz is my favourite implementation of
it.

> After spending a couple of minutes reading on
> it, my gut feeling is that turning it rsyncable in any meaningful way
> will greatly hurt the compression ratios you're used to seeing from it,
> negating the reason you wanted to use it to begin with. It achieves
> better compression ratios by having a very big lookback buffer (encoded
> as a dictionary), which is the exact opposite of rsyncability.

I see, OK.

Regards,

	Shlomi Fish

-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
Chuck Norris/etc. Facts - http://www.shlomifish.org/humour/bits/facts/

Writing a BitKeeper replacement is probably easier at this point than getting 
its license changed.
    — Matt Mackall (who ended up writing a BitKeeper replacement)

Please reply to list if it's a mailing list post - http://shlom.in/reply .

Re: Typo Report in Man Page - "fro stdin" and Question

[Shachar Shemesh <shachar@sh...>]

On 06/21/2012 06:06 PM, Shlomi Fish wrote:
>> But despair not. You can achieve the equivalent level of security by
>> encrypting your private key with a password, and storing it using the
>> same provider you store your actual data. At this point in time
>> rsyncrypto does not support decrypting from password protected RSA keys,
>> but such support can be, fairly easily, added. Otherwise, in case of
>> catastrophe, you can simply pull your encrypted key and decrypt is locally.
>>
> Thanks! I think that is also what Harold suggested.
Same end result, give or take. Different mechanism.

RSA keys can be encrypted via a fairly standard fashion that has nothing
to do with pgp or gpg. Openssl knows how to open such encrypted keys,
and so will a future version of rsyncrypto.
>
> BTW, do you think it would be possible to write an --rsyncable patch for xz
> instead of gzip (see http://tukaani.org/xz/ ; http://en.wikipedia.org/wiki/Xz )
I think you meant LZMA. After spending a couple of minutes reading on
it, my gut feeling is that turning it rsyncable in any meaningful way
will greatly hurt the compression ratios you're used to seeing from it,
negating the reason you wanted to use it to begin with. It achieves
better compression ratios by having a very big lookback buffer (encoded
as a dictionary), which is the exact opposite of rsyncability.

Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com

Re: Typo Report in Man Page - "fro stdin" and Question

[Shlomi Fish <shlomif@sh...>]

Hi Shachar,

sorry for the late response.

On Fri, 15 Jun 2012 17:01:51 +0300
Shachar Shemesh <shachar@...> wrote:

> On 06/15/2012 12:48 PM, Shlomi Fish wrote:
> > Hi all,
> >
> > thanks for rsyncrypto.
> you are welcome.
> >
> > I've become interested in it because I recently decided to use remote
> > backups on http://rsync.net/ and want to keep my backups' secure. The first
> > thing I wanted to note is that as of the latest release of rsyncrypto (1.12),
> > the man page reads "fro stdin" instead of "from stdin". I saw this is fixed in
> > the Subversion repository, so isn’t it time for a new release?
> The subversion contains some fairly major changes which I have not had
> the time to complete. I will release when they are ready. Hopefully,
> I'll have more time for rsyncrypto soon.

I see, thanks for the heads’ up.

> > Otherwise I wanted to ask a question: what I want to do is have the encoded
> > data encrypted by a password, which I enter for encrypting and for
> > decrypting, so that I can still unpack/decode it if I just have access to the
> > encoded data. How can this be achieved while still making the encoded data
> > rsync-friendly? Does rsyncrypto support something like that? Should I look for
> > something else?
> Rsyncrypto uses a public/private key as the master encryption key, with
> each file being encrypted using a symmetrical (AES) key. While it is
> possible to produce an (insecure) symmetrical key from a password, no
> such method exists for public keys. As such, no, rsyncrypto does not
> support this mode of use.

OK.

> 
> But despair not. You can achieve the equivalent level of security by
> encrypting your private key with a password, and storing it using the
> same provider you store your actual data. At this point in time
> rsyncrypto does not support decrypting from password protected RSA keys,
> but such support can be, fairly easily, added. Otherwise, in case of
> catastrophe, you can simply pull your encrypted key and decrypt is locally.
> 

Thanks! I think that is also what Harold suggested.

BTW, do you think it would be possible to write an --rsyncable patch for xz
instead of gzip (see http://tukaani.org/xz/ ; http://en.wikipedia.org/wiki/Xz )
in order to achieve better compression (and as a result faster
uploads/downloads) and to adapt rsyncrypto to it? 

Regards,

	Shlomi Fish 

-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
http://www.shlomifish.org/humour/ways_to_do_it.html

We don’t know his cellphone number, and even if we did, we would tell you that
we didn’t know it.

Please reply to list if it's a mailing list post - http://shlom.in/reply .