rsyncrypto-devel — Development discussions, bug reports, and announcements for rsyncrypto

Rsyncrypto and openssl-0.9.8c+

[Milton C. <mi...@ca...>]

Hi all,

I was starting to use rsyncrypto when my distro updated from openssl-0.9.8b to openssl-0.9.8e.
Once that happens, rsyncrypto dumps core.

1st question: are any of you using openssl-0.9.8c or newer?

I've tracked the problem down to a call to AES_cbc_encrypt() in aes_crypt.cpp:99.
rsyncrypto dumps core when there is part of a file left and we are trying to encrypt a
block that is less than 16 chars.

I'm going to try using a static block of 16 chars to see if that gets me past the seg fault.

-- 
Milton Calnek BSc, A/Slt(Ret.)
mi...@ca...
306-382-3657


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Partial transfer of rsyncrypto encrypted files

[Shachar S. <sh...@sh...>]

Jan Alphenaar wrote:
>
> Shachar,
>
>  
>
> Ok, mystery solved. After the file is encrypted for the first time, my 
> script deletes the key file. When the file is encrypted a second time, 
> rsyncrypto creates a new key file, and also generates a completely new 
> encrypted output file (that is why rsync is fully transferring the 
> file again).
>
>  
>
> If the key file is not deleted, rsyncrypto delivers the same output 
> file, so rsync can use the rsync algorithm.
>
>  
>
> This leaves me here with one question. Is it possible to have the same 
> encrypted file without keeping the key file on my pc ?
>
>  
>
> Thanks for the replies.
>
>  
>
> Regards,
>
>  
>
> Jan
>
>  
>
Rsyncrypto, while doing lots of stuff differently, is still modeled 
after the classic encryption method. This means that there is one 
asymmetric key to unlock all the files, but each file is encrypted with 
its own symmetric (or "session") key. This is done for security 
considerations, and cannot be turned off without some serious rethinking 
of the security of the process.

If you delete the session key, the only place it is kept is, encrypted, 
inside the encrypted file. In fact, it is this re-encryption of the 
session key that is the header that changes between encryptions. If you 
just run rsyncrypto again, a new session key will be generated, and, 
obviously, the file will look completely different.

All is not lost. If you have the RSA private key and the old encrypted 
file, you can use rsyncrypto to recover the previous session key. Simply 
perform a decryption, and the session key will be generated. Then use 
that same session key to encrypt again.

Of course, with the session key being 68 bytes and your encrypted file 
being 1GB, the simplest thing to do is just keep the session key around 
and not erase it.

Shachar


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

Re: Partial transfer of rsyncrypto encrypted files

[Julian P. R. <jul...@gm...>]

Sounds like the files are totally different... silly question: is gzip
patched with the rsyncable flag?Can you use a hex compare tool to confirm
that most of the files are the same?

On Fri, Jul 31, 2009 at 11:58 AM, Shachar Shemesh <sh...@sh...>wrote:

>  Jan Alphenaar wrote:
>
>  Julian,
>
>
>
> Both scenario’s you describe are the way rsync should behave, but it does
> not. Let me just describe how case a can be reproduced.
>
>
>
> Take a large zip file, my file is now 100MB, and encrypt it with
> rsyncrypto. Now rename that file to 1.zip. Encrypt this file again and
> rename the encrypted file to 2.zip. Both files should be the same (except
> the first blocks), right ?
>
> That really depends on whether you encrypted them using the same session
> key.
>
>
> Hope it is a bit more clear now.
>
>
>
> Regards,
>
>
>
> Jan
>
>
>
> Here is what I'm testing.
>
> dd if=/dev/urandom of=/tmp/test bs=$((1024*1024)) count=100
>
>
> Create a 100MB random file.
>
> sun@sunlap:/tmp$ rsyncrypto test test1.enc test.key
> /usr/share/doc/rsyncrypto/examples/tests/cert.crt
> sun@sunlap:/tmp$ rsyncrypto test test2.enc test.key
> /usr/share/doc/rsyncrypto/examples/tests/cert.crt
>
> Create two files which are (almost) identical. vbindiff confirms this - the
> two files have a different header, but several bytes into the file they
> become identical and remain so until the end of the file.
>
> If this is your situation, rsyncrypto is working as advertised. If rsync
> does not do the expected thing with this case (for example, because it does
> not apply the rsync algorithm to files that start off differently but become
> identical in cases of partial transfers), then this is a rsync bug, and has
> nothing to do with rsyncrypto.
>
> Shachar
>
> --
> Shachar Shemesh
> Lingnu Open Source Consulting Ltd.http://www.lingnu.com
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Rsyncrypto-devel mailing list
> Rsy...@li...
> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>
>

Re: Partial transfer of rsyncrypto encrypted files

[Shachar S. <sh...@sh...>]

Jan Alphenaar wrote:
>
> Julian,
>
>  
>
> Both scenario's you describe are the way rsync should behave, but it 
> does not. Let me just describe how case a can be reproduced.
>
>  
>
> Take a large zip file, my file is now 100MB, and encrypt it with 
> rsyncrypto. Now rename that file to 1.zip. Encrypt this file again and 
> rename the encrypted file to 2.zip. Both files should be the same 
> (except the first blocks), right ?
>
That really depends on whether you encrypted them using the same session 
key.
>
>
> Hope it is a bit more clear now.
>
>  
>
> Regards,
>
>  
>
> Jan
>


Here is what I'm testing.

> dd if=/dev/urandom of=/tmp/test bs=$((1024*1024)) count=100

Create a 100MB random file.

> sun@sunlap:/tmp$ rsyncrypto test test1.enc test.key 
> /usr/share/doc/rsyncrypto/examples/tests/cert.crt
> sun@sunlap:/tmp$ rsyncrypto test test2.enc test.key 
> /usr/share/doc/rsyncrypto/examples/tests/cert.crt
Create two files which are (almost) identical. vbindiff confirms this - 
the two files have a different header, but several bytes into the file 
they become identical and remain so until the end of the file.

If this is your situation, rsyncrypto is working as advertised. If rsync 
does not do the expected thing with this case (for example, because it 
does not apply the rsync algorithm to files that start off differently 
but become identical in cases of partial transfers), then this is a 
rsync bug, and has nothing to do with rsyncrypto.

Shachar

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

Re: Partial transfer of rsyncrypto encrypted files

[Julian P. R. <jul...@gm...>]

Case A:Rsync still has to start from the beginning, but it uses the partial
file as a basis file, so transfer of the first part should be much faster
than transferring from scratch. Rsync will NOT do what you are thinking and
use the same file and just continue building on it, but it will start a new
file, leaving the "partial" file there until the new one is completely
rebuilt, after which the partial one is deleted.

Case B:
Same issue really here... Re-encrypting will generate a new file with new
mod timestamp. Again it will be uploaded using already present file as a
basis, making the transfer much faster, but the whole file will be rebuilt
on the destination (of course be using large chunks of the basis file, which
is what will speed it up).

On Thu, Jul 30, 2009 at 11:33 PM, Jan Alphenaar <jan...@do...
> wrote:

> Hi,
>
> I was recently playing around with rsyncrypto and rsync and found some
> interesting behavior during one of my large file transfers.
>
> This is the situation. After encrypting my large file (approximately 1GB),
> rsync starts copying this file to my server. Here is the rsync command
> used,
> I modified it a bit to make it easier to read. Note, the "partial" option
> is
> used. In case the transfer is interrupted, rsync leaves the partially
> transferred file on the server.
>
> rsync -rlt -v --partial -e ssh Test.zip jan@<servername>:/data
>
> Half way down I interrupt the transfer, the partially transferred file
> stays
> on the server as expected. In the next session the file is again encrypted
> with rsyncrypto. Then I start a new rsync copy of the file, expecting rsync
> would continue with the partially transferred file, but it does not, it
> starts over at the beginning. Lets call this case a.
>
> It becomes even more fuzzy. Consider the following case (b). When I encrypt
> a large file with rsyncrypto and fully transfer it to my server. After
> transferring, I am going to encrypt my file again. Start a new transfer of
> the newly encrypted file. Now rsync is not copying over the file, fully
> making use of the rsync algorithm.
>
> I know it looks like an rsync issue, but the rsync behavior is correct if
> the file is not encrypted a second time. Then is does not start at the
> beginning (but at the end) the second time it tries to copy a large file.
>
> Can anybody explain this behaviour, cause I am totally in the dark with
> this
> behavior.
>
> Any help is greatly appreciated.
>
> Warm regards,
>
> Jan
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Rsyncrypto-devel mailing list
> Rsy...@li...
> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>

Re: Partial transfer of rsyncrypto encrypted files

[Robin L. P. <rlp...@di...>]

On Thu, Jul 30, 2009 at 11:33:10PM +0200, Jan Alphenaar wrote:
> Hi,
> 
> I was recently playing around with rsyncrypto and rsync and found
> some interesting behavior during one of my large file transfers.
> 
> This is the situation. After encrypting my large file
> (approximately 1GB), rsync starts copying this file to my server.
> Here is the rsync command used, I modified it a bit to make it
> easier to read. Note, the "partial" option is used. In case the
> transfer is interrupted, rsync leaves the partially transferred
> file on the server.
> 
> rsync -rlt -v --partial -e ssh Test.zip jan@<servername>:/data
> 
> Half way down I interrupt the transfer, the partially transferred
> file stays on the server as expected. In the next session the file
> is again encrypted with rsyncrypto. Then I start a new rsync copy
> of the file, expecting rsync would continue with the partially
> transferred file, but it does not, it starts over at the
> beginning. Lets call this case a.

If you let it keep going for a while, does the apparent speed (use
"-P" instead of partial and it'll do partial and show you the
progress) speed up a whole great big bunch?  I expect that it will.

IIRC, the first few blocks in an rsyncrypto encrypted file are
always different, but the rest of the file is the same.

-Robin

Re: Seg Fault - Core Dump.

[Shachar S. <sh...@sh...>]

Milton Calnek wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I'm hoping you folks can help. A couple of weeks ago, I built/installed
> rsyncrypto-1.12. I tried it out and it seemed to work as advertised.
>
> I put it down for a couple of weeks and tried it out again today... now
> I get seg faults and core files. Yes, several libraries and a kernel have
> been updated, but I have tried re-compiling and re-installing... this has
> not helped (much).
>
> As far as upgrades, among others, I noticed that I went from openssl-0.9.8b
> to openssl-0.9.8e.
>
> There's a bunch of entries in the stack trace that doesn't have useful
> info. Any idea on how to get the info?
>
> Any hints/suggestions would be appreciated.
>
> Thanks.
>
> GDB output:
> warning: Can't read pathname for load map: Input/output error.
> Reading symbols from /usr/lib/libargtable2.so.0...done.
> Loaded symbols for /usr/lib/libargtable2.so.0
> Reading symbols from /lib/libcrypto.so.6...done.
> Loaded symbols for /lib/libcrypto.so.6
> Reading symbols from /usr/lib/libstdc++.so.6...done.
> Loaded symbols for /usr/lib/libstdc++.so.6
> Reading symbols from /lib/libm.so.6...done.
> Loaded symbols for /lib/libm.so.6
> Reading symbols from /lib/libgcc_s.so.1...done.
> Loaded symbols for /lib/libgcc_s.so.1
> Reading symbols from /lib/libc.so.6...done.
> Loaded symbols for /lib/libc.so.6
> Reading symbols from /lib/libdl.so.2...done.
> Loaded symbols for /lib/libdl.so.2
> Reading symbols from /usr/lib/libz.so.1...done.
> Loaded symbols for /usr/lib/libz.so.1
> Reading symbols from /lib/ld-linux.so.2...done.
> Loaded symbols for /lib/ld-linux.so.2
> Core was generated by `rsyncrypto -r /home /tmp/home /tmp/keys/home /root/.keys/rckey.crt'.
> Program terminated with signal 11, Segmentation fault.
> [New process 29995]
> #0  0x00384a22 in AES_cbc_encrypt () from /lib/libcrypto.so.6
> (gdb) bt
> #0  0x00384a22 in AES_cbc_encrypt () from /lib/libcrypto.so.6
> #1  0x00c02340 in _dl_map_object () from /lib/ld-linux.so.2
> #2  0x091ab3d0 in ?? ()
> #3  0x091ab250 in ?? ()
> #4  0x00000005 in ?? ()
> #5  0xbff576a0 in ?? ()
> #6  0x00000000 in ?? ()
> (gdb)
>
>
>
> I also ran strace and here is the tail end:
> open("/tmp/home/milton/Desktop/.directory.rsyncrypto_tmp", O_RDWR|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 8
> _llseek(8, 196, [196], SEEK_SET)        = 0
> pipe([9, 10])                           = 0
> clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb7f35928) = 10337
> - --- SIGCHLD (Child exited) @ 0 (0) ---
> close(7)                                = 0
> close(10)                               = 0
> read(9, "\37\213\10\0!\225\266I\0\3\213vI-\316.\311/Pp\315+)\252\214\345r\315K\316O\311"..., 8192) = 85
> read(9, "", 8192)                       = 0
> close(9)                                = 0
> - --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
>   
The core seems useless. The strace as pasted is also useless. Please run 
with -f and -o, and send me (private, after compressing it) the output.

Also, which OS, if Linux, which distro, and which version. In 
particular, what versions of openssl and argtable.

Thanks,
Shachar

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

Seg Fault - Core Dump.

[Milton C. <mi...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm hoping you folks can help. A couple of weeks ago, I built/installed
rsyncrypto-1.12. I tried it out and it seemed to work as advertised.

I put it down for a couple of weeks and tried it out again today... now
I get seg faults and core files. Yes, several libraries and a kernel have
been updated, but I have tried re-compiling and re-installing... this has
not helped (much).

As far as upgrades, among others, I noticed that I went from openssl-0.9.8b
to openssl-0.9.8e.

There's a bunch of entries in the stack trace that doesn't have useful
info. Any idea on how to get the info?

Any hints/suggestions would be appreciated.

Thanks.

GDB output:
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libargtable2.so.0...done.
Loaded symbols for /usr/lib/libargtable2.so.0
Reading symbols from /lib/libcrypto.so.6...done.
Loaded symbols for /lib/libcrypto.so.6
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Core was generated by `rsyncrypto -r /home /tmp/home /tmp/keys/home /root/.keys/rckey.crt'.
Program terminated with signal 11, Segmentation fault.
[New process 29995]
#0  0x00384a22 in AES_cbc_encrypt () from /lib/libcrypto.so.6
(gdb) bt
#0  0x00384a22 in AES_cbc_encrypt () from /lib/libcrypto.so.6
#1  0x00c02340 in _dl_map_object () from /lib/ld-linux.so.2
#2  0x091ab3d0 in ?? ()
#3  0x091ab250 in ?? ()
#4  0x00000005 in ?? ()
#5  0xbff576a0 in ?? ()
#6  0x00000000 in ?? ()
(gdb)



I also ran strace and here is the tail end:
open("/tmp/home/milton/Desktop/.directory.rsyncrypto_tmp", O_RDWR|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 8
_llseek(8, 196, [196], SEEK_SET)        = 0
pipe([9, 10])                           = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb7f35928) = 10337
- --- SIGCHLD (Child exited) @ 0 (0) ---
close(7)                                = 0
close(10)                               = 0
read(9, "\37\213\10\0!\225\266I\0\3\213vI-\316.\311/Pp\315+)\252\214\345r\315K\316O\311"..., 8192) = 85
read(9, "", 8192)                       = 0
close(9)                                = 0
- --- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++



- --
Milton Calnek BSc, A/Slt(Ret.)
mi...@ca...
306-382-3657

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFJ5P8jHgnbf2T2QqMRAk6FAJ0ZGPUJ/JQUEucHE9Is3XjebQ+zTwCeJgTd
sb4vl04G6ZCqwOnsolXxM2c=
=X+N4
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

join.

[Milton C. <mi...@ca...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

join.
- --
Milton Calnek BSc, A/Slt(Ret.)
mi...@ca...
306-382-3657

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFJ5PloHgnbf2T2QqMRAlitAJ96xNX08xI2J33ZKBhr1XIeibcnNACgzcN+
PBiOZ+9ggXzYZnUaML2ZACY=
=k1Mt
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Generating public key using openssl

[Piotr M. <zax...@gm...>]

This, with the "-config openssl.cnf" option to the below command, solve the
problem.

Thanks!
Zax

On Wed, Feb 18, 2009 at 14:55, Julian Pace Ross
<jul...@gm...>wrote:

> Try putting attached file in the same dir as openssl.exe
>
> On Wed, Feb 18, 2009 at 2:52 PM, Piotr Martyniuk <zax...@gm...>wrote:
>
>> Hi Shachar,
>>
>> I'm trying to generate the public key using openssl as it is written in
>> the attached rsyncrypto.html file:
>>
>> openssl req -nodes -newkey rsa:1536 -x509 -keyout backup.key -out
>> backup.crt
>>
>> Unfortunately when I do this I'm getting below error:
>>
>> Unable to load config info from /usr/local/ssl/openssl.cnf
>>
>> The problem is that this config file is not available in the rsyncrypto
>> package (I used ver 1.06 under Windows and also the one provided by Julian).
>>
>> Regards,
>> Zax
>>
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
>> CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source
>> participation
>> -Receive a $600 discount off the registration fee with the source code:
>> SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Rsyncrypto-devel mailing list
>> Rsy...@li...
>> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>>
>>
>

Re: Why no ZIP version for Windows anymore?

[Julian P. R. <jul...@gm...>]

For the same reason I have a compiling version of 1.06 that has been patched
with most of the changes between 1.06 and 1.12... In this way I have a
'portable' version with more or less the latest bug fixes and features...
Email me if you're interested.

On Wed, Feb 18, 2009 at 11:43 AM, Piotr Martyniuk <zax...@gm...>wrote:

> Hi Shachar,
>
> The answer is actually in the archives.
>
>
> Yes, I found it now.
>
>
>> I switched to a new compiler (Visual Studio 9), and it requires runtime
>> libraries that can only be installed with an installer. As such, I switched
>> the entire distribution to an installer based one.
>
>
> Is there a way to make rsyncrypto portable the way it was up to the version
> 1.06? For me it is OK if I install it on my machine at home, but then I
> would like to use it also at work where I have no admin rights to install it
> properly. I try to copy the files from the folder where the rsyncrypto was
> installed on my local machine, but this cause an execution errors.
>
>
>> Do feel free to compile the program yourself with a compiler that does not
>> have such strict runtime libraries requirements.
>
>
> I'm afraid that this is bit too much for my skills. I try to compile it
> using a MinGW package, but it was not successful as it is requires lot of
> dependent libraries. I try to compile it under Cygwin, but it is bit too
> much to carry around on the USB stick justo to have the rsyncrypto.
>
> Regards,
> Zax
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Rsyncrypto-devel mailing list
> Rsy...@li...
> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>
>

Generating public key using openssl

[Piotr M. <zax...@gm...>]

Hi Shachar,

I'm trying to generate the public key using openssl as it is written in the
attached rsyncrypto.html file:

openssl req -nodes -newkey rsa:1536 -x509 -keyout backup.key -out backup.crt

Unfortunately when I do this I'm getting below error:

Unable to load config info from /usr/local/ssl/openssl.cnf

The problem is that this config file is not available in the rsyncrypto
package (I used ver 1.06 under Windows and also the one provided by Julian).

Regards,
Zax

Re: Why no ZIP version for Windows anymore?

[Michal S. <hra...@ce...>]

2009/2/18 Julian Pace Ross <jul...@gm...>:
> That would be great... if anything, definitely for the executable... not
> sure whether you'd want to have two streams of sources to maintain though...
> In any case I obviously have no problem with uploading the whole lot...
>

You can make it a branch but is it really necessary?

If the latest source does not build I guess it is a bug that should be
fixed, and then all there will be is a MSI binary and a portable
binary.

Not that I care too much, I personally do not use either binary right now.

Thanks

Michal

Re: Why no ZIP version for Windows anymore?

[Piotr M. <zax...@gm...>]

On Wed, Feb 18, 2009 at 12:03, Julian Pace Ross
<jul...@gm...>wrote:

> Don't think it's a good idea... there should just be one version to avoid
> confusion.
>

Maybe with some info on the project web page this could work. :)

Regards,
Zax

Re: Why no ZIP version for Windows anymore?

[Julian P. R. <jul...@gm...>]

That would be great... if anything, definitely for the executable... not
sure whether you'd want to have two streams of sources to maintain though...
In any case I obviously have no problem with uploading the whole lot...

On Wed, Feb 18, 2009 at 1:44 PM, Shachar Shemesh <sh...@sh...>wrote:

> Piotr Martyniuk wrote:
>
>>
>>
>> On Wed, Feb 18, 2009 at 12:03, Julian Pace Ross <
>> jul...@gm... <mailto:jul...@gm...>> wrote:
>>
>>    Don't think it's a good idea... there should just be one version
>>    to avoid confusion.
>>
>>
>> Maybe with some info on the project web page this could work. :)
>>
> It's a wiki - feel free to add it.
>
> Julian, I'll gladly give you upload access to the sourceforge site.
>
> Shachar
>
>

Re: Why no ZIP version for Windows anymore?

[Shachar S. <sh...@sh...>]

Piotr Martyniuk wrote:
>
>
> On Wed, Feb 18, 2009 at 12:03, Julian Pace Ross 
> <jul...@gm... <mailto:jul...@gm...>> wrote:
>
>     Don't think it's a good idea... there should just be one version
>     to avoid confusion.
>
>
> Maybe with some info on the project web page this could work. :)
It's a wiki - feel free to add it.

Julian, I'll gladly give you upload access to the sourceforge site.

Shachar

Re: Why no ZIP version for Windows anymore?

[Julian P. R. <jul...@gm...>]

Don't think it's a good idea... there should just be one version to avoid
confusion.

On Wed, Feb 18, 2009 at 12:00 PM, Piotr Martyniuk <zax...@gm...>wrote:

> Maybe it would be possible to store your version on the sourceforge as
> well, so more people could use your version.
>
> Regards,
> Zax
>
> On Wed, Feb 18, 2009 at 11:51, Julian Pace Ross <jul...@gm...
> > wrote:
>
>> For the same reason I have a compiling version of 1.06 that has been
>> patched with most of the changes between 1.06 and 1.12... In this way I have
>> a 'portable' version with more or less the latest bug fixes and features...
>> Email me if you're interested.
>>
>> On Wed, Feb 18, 2009 at 11:43 AM, Piotr Martyniuk <zax...@gm...>wrote:
>>
>>> Hi Shachar,
>>>
>>> The answer is actually in the archives.
>>>
>>>
>>> Yes, I found it now.
>>>
>>>
>>>> I switched to a new compiler (Visual Studio 9), and it requires runtime
>>>> libraries that can only be installed with an installer. As such, I switched
>>>> the entire distribution to an installer based one.
>>>
>>>
>>> Is there a way to make rsyncrypto portable the way it was up to the
>>> version 1.06? For me it is OK if I install it on my machine at home, but
>>> then I would like to use it also at work where I have no admin rights to
>>> install it properly. I try to copy the files from the folder where the
>>> rsyncrypto was installed on my local machine, but this cause an execution
>>> errors.
>>>
>>>
>>>> Do feel free to compile the program yourself with a compiler that does
>>>> not have such strict runtime libraries requirements.
>>>
>>>
>>> I'm afraid that this is bit too much for my skills. I try to compile it
>>> using a MinGW package, but it was not successful as it is requires lot of
>>> dependent libraries. I try to compile it under Cygwin, but it is bit too
>>> much to carry around on the USB stick justo to have the rsyncrypto.
>>>
>>> Regards,
>>> Zax
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
>>> CA
>>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>>> Enterprise
>>> -Strategies to boost innovation and cut costs with open source
>>> participation
>>> -Receive a $600 discount off the registration fee with the source code:
>>> SFAD
>>> http://p.sf.net/sfu/XcvMzF8H
>>> _______________________________________________
>>> Rsyncrypto-devel mailing list
>>> Rsy...@li...
>>> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>>>
>>>
>>
>

Re: Why no ZIP version for Windows anymore?

[Piotr M. <zax...@gm...>]

Maybe it would be possible to store your version on the sourceforge as well,
so more people could use your version.

Regards,
Zax

On Wed, Feb 18, 2009 at 11:51, Julian Pace Ross
<jul...@gm...>wrote:

> For the same reason I have a compiling version of 1.06 that has been
> patched with most of the changes between 1.06 and 1.12... In this way I have
> a 'portable' version with more or less the latest bug fixes and features...
> Email me if you're interested.
>
> On Wed, Feb 18, 2009 at 11:43 AM, Piotr Martyniuk <zax...@gm...>wrote:
>
>> Hi Shachar,
>>
>> The answer is actually in the archives.
>>
>>
>> Yes, I found it now.
>>
>>
>>> I switched to a new compiler (Visual Studio 9), and it requires runtime
>>> libraries that can only be installed with an installer. As such, I switched
>>> the entire distribution to an installer based one.
>>
>>
>> Is there a way to make rsyncrypto portable the way it was up to the
>> version 1.06? For me it is OK if I install it on my machine at home, but
>> then I would like to use it also at work where I have no admin rights to
>> install it properly. I try to copy the files from the folder where the
>> rsyncrypto was installed on my local machine, but this cause an execution
>> errors.
>>
>>
>>> Do feel free to compile the program yourself with a compiler that does
>>> not have such strict runtime libraries requirements.
>>
>>
>> I'm afraid that this is bit too much for my skills. I try to compile it
>> using a MinGW package, but it was not successful as it is requires lot of
>> dependent libraries. I try to compile it under Cygwin, but it is bit too
>> much to carry around on the USB stick justo to have the rsyncrypto.
>>
>> Regards,
>> Zax
>>
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
>> CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source
>> participation
>> -Receive a $600 discount off the registration fee with the source code:
>> SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Rsyncrypto-devel mailing list
>> Rsy...@li...
>> https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel
>>
>>
>

Re: Why no ZIP version for Windows anymore?

[Piotr M. <zax...@gm...>]

Hi Shachar,

The answer is actually in the archives.


Yes, I found it now.


> I switched to a new compiler (Visual Studio 9), and it requires runtime
> libraries that can only be installed with an installer. As such, I switched
> the entire distribution to an installer based one.


Is there a way to make rsyncrypto portable the way it was up to the version
1.06? For me it is OK if I install it on my machine at home, but then I
would like to use it also at work where I have no admin rights to install it
properly. I try to copy the files from the folder where the rsyncrypto was
installed on my local machine, but this cause an execution errors.


> Do feel free to compile the program yourself with a compiler that does not
> have such strict runtime libraries requirements.


I'm afraid that this is bit too much for my skills. I try to compile it
using a MinGW package, but it was not successful as it is requires lot of
dependent libraries. I try to compile it under Cygwin, but it is bit too
much to carry around on the USB stick justo to have the rsyncrypto.

Regards,
Zax

Re: Why no ZIP version for Windows anymore?

[Shachar S. <sh...@sh...>]

Piotr Martyniuk wrote:
> Hi,
>
> I see that since a version 1.06 there is no new version packed as ZIP 
> archive, which was running on the system where the admin rights were 
> revoked, so this version was working as a portable version.
> I wonder why now only the MSI packages are available. Is it possible 
> to get the latest version as the ZIP archive as well?
>
> Regards,
> Zax
Hi Zax,

The answer is actually in the archives.

I switched to a new compiler (Visual Studio 9), and it requires runtime 
libraries that can only be installed with an installer. As such, I 
switched the entire distribution to an installer based one.

Do feel free to compile the program yourself with a compiler that does 
not have such strict runtime libraries requirements.

Shachar

Why no ZIP version for Windows anymore?

[Piotr M. <zax...@gm...>]

Hi,

I see that since a version 1.06 there is no new version packed as ZIP
archive, which was running on the system where the admin rights were
revoked, so this version was working as a portable version.
I wonder why now only the MSI packages are available. Is it possible to get
the latest version as the ZIP archive as well?

Regards,
Zax

Re: New anti-spam measures on the web site

[Shachar S. <sh...@sh...>]

Robin Lee Powell wrote:
> On Mon, Dec 01, 2008 at 08:49:59PM +0200, Shachar Shemesh wrote:
>   
>> We now return to your usual silence.... :-D
>>     
>
> You should take it as a compliment!  I haven't been saying anything
> because everything's working just fine!
>
>   
I was actually referring to my silence. Since promising you a new, 
non-backwards compatible version I retrofitted Unicode into rsyncrypto 
AND the library it uses to parse command line arguments, and then dumped 
the code and went a different path, only to now wonder whether the 
original idea was more correct. Updates when I (finally) make up my mind....

Shachar

Re: New anti-spam measures on the web site

[Robin L. P. <rlp...@di...>]

On Mon, Dec 01, 2008 at 08:49:59PM +0200, Shachar Shemesh wrote:
> We now return to your usual silence.... :-D

You should take it as a compliment!  I haven't been saying anything
because everything's working just fine!

-Robin

-- 
They say:  "The first AIs will be built by the military as weapons."
And I'm thinking:  "Does it even occur to you to try for something
other than the default outcome?" -- http://shorl.com/tydruhedufogre
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

New anti-spam measures on the web site

[Shachar S. <sh...@sh...>]

Hi all,

The web site for the project (yes, there is a web site - 
http://rsyncrypto.lingnu.com) is a wiki, which has been open to public 
anonymous editing
up until now. I have now given up. The spammers are vandalizing it too 
frequently. From now on editing is only possible for people who create 
an account. It is possible for everyone to create an account, so don't 
be shy :-)

We now return to your usual silence.... :-D

Shachar

Re: Incompatible changes in the next version of rsyncrypto

[Robin L. P. <rlp...@di...>]

On Mon, Oct 13, 2008 at 11:33:20AM +0200, Shachar Shemesh wrote:
> Hi all,
> 
> This is a heads up, as well as a chance for you to give some
> input, about two incompatible changes I'm planning for the next
> version of rsyncrypto.
> 
> The first change has to do with the "--file-list" option, that
> allows giving a list of files to be processed. At the moment,
> --file-list is a parameter less option, and it merely changes the
> meaning of the first argument from being the actual source file,
> to being a list of files that are used as source. If the first
> argument is "-", this means that the list is read from standard
> input.
> 
> The problem begins when the --name-encrypt option is used for
> either decryption or encryption. With this option, the directory
> in relation to which the names are interpreted is crucial. The
> current scheme leave no other option than "the current directory".
> However, asking the client to change the current directory as part
> of the program's arguments seems a bit of an onus requirement.
> 
> The change I am planning is to have --file-list accept a single
> parameter saying "which file to use", with "-" meaning stdin as
> before. The first argument to rsyncrypto will now be the directory
> in relation to which the names given in the file list are
> interpreted.

That will break my scripts.  It's also the right thing to do.  Go
for it!

-Robin

-- 
They say:  "The first AIs will be built by the military as weapons."
And I'm thinking:  "Does it even occur to you to try for something
other than the default outcome?" -- http://shorl.com/tydruhedufogre
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/