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

RE: File size zero after decrypting with wrong certificate

[Jan A. <jan...@do...>]

Hi Shachar,

 

I was just having a look at some old questions I had regarding rsyncrypto.

 

One of them is described in the email below. Would it be possible to remove
the tmp file and add the filename in the error message ?

 

Regards,

 

Jan

 

  _____  

Van: Jan Alphenaar [mailto:jan...@do...] 
Verzonden: donderdag 24 juli 2008 22:03
Aan: 'L-rsyncrypto'
CC: 'Shachar Shemesh'
Onderwerp: RE: File size zero after decrypting with wrong certificate

 

Hi again,

 

I have just tested RsynCrypto version 1.12 (on WinXP) for this issue (see
email below). 

 

Rsyncrypto indeed works with a tmp file now. After the error message is
generated, rsyncrypto bails out, leaving my original file intact. But it
also leaves the tmp file on my disc. Would it be possible to delete it ?

 

Another thing I noticed, is that the filename is now removed from the error
message.

 

==== BEGIN OUTPUT =====

D:\Test>"D:\test\RsynCrypto\RsynCrypto.exe" -d
"D:\Test\EncryptedFiles\testfile.pdf" "D:\Test\ClearFiles\testfile.pdf"
"D:\Test\keys\testfile.pdf" "D:\Test\Certificate\Cert.key"

error:0407A079:rsa routines:RSA_padding_check_PKCS1_OAEP:oaep decoding error

===== END OUTPUT ======

 

Thanks in advance.

 

Regards,

 

Jan

 

 

  _____  

Van: Jan Alphenaar [mailto:jan...@do...] 
Verzonden: zaterdag 19 juli 2008 11:44
Aan: 'L-rsyncrypto'
CC: 'Shachar Shemesh'
Onderwerp: File size zero after decrypting with wrong certificate

 

Hi Sachar,

 

Sorry for keeping you busy lately. I now have some kind of theoretical
question.

 

When I encrypt my file with a certificate, let's say certificate A. And I
copy this encrypted file to a CD. Assume I do this on a daily basis. At some
point in time my certificate gets corrupted and I have to generate a new one
(certificate B). This would obviously make my in the past created backups
useless...

 

Now I start creating backups with this new certificate for the next couple
of months, so far so good. Then something happens and I decide to restore
(decrypt) a file from the CD. But - silly me - I use a file which is
encrypted with certificate A, resulting in the following rsyncrypto error.

 

======== BEGIN OUTPUT ========

"D:\Restore\test001.txt" error:0407A079:rsa
routines:RSA_padding_check_PKCS1_OAEP:oaep decoding error:

========= END OUTPUT =========

 

The file which needed to be overwritten was still on my disk before I did
this, but after the decryption my file has size 0, leaving me with nothing.

 

Would it be possible/desirable to make rsyncrypto generate an error message
and leave the file intact when it tries to decrypt a file with the wrong
certificate, in stead of zeroing it out?

 

Warm regards,

 

Jan

 

RE: Rsyncrypto error message

[Jan A. <jan...@do...>]

Hi Shachar,

Another thing from the past was the issue written down below.

The error message works, but the tmp file remains on the disk. Would it be
possible to remove the tmp file ?

Regards,

Jan

-----Oorspronkelijk bericht-----
Van: Jan Alphenaar [mailto:jan...@do...] 
Verzonden: donderdag 24 juli 2008 21:20
Aan: 'Shachar Shemesh'
CC: 'L-rsyncrypto'
Onderwerp: RE: Rsyncrypto error message

Sachar,

Nice, it works...

This is the output of the test.

====== BEGIN OUTPUT ======
D:\Test>"D:\test\RsynCrypto\RsynCrypto.exe" D:\Test\ClearFiles\testfile.pdf"
"D:\Test\EncryptedFiles\testfile.pdf" "D:\Test\keys\testfile.pdf"
"D:\Test\Certificate\Cert.crt"
rename failed(D:\Test\EncryptedFiles\testfile.pdf): Permission denied
======= END OUTPUT =======

Thanks !

Regards,

Jan

-----Oorspronkelijk bericht-----
Van: Shachar Shemesh [mailto:sh...@sh...] 
Verzonden: dinsdag 22 juli 2008 7:20
Aan: Jan Alphenaar
CC: 'L-rsyncrypto'
Onderwerp: Re: Rsyncrypto error message

Jan Alphenaar wrote:
>
> Hi Sachar,
>
>  
>
> I have another question regarding error messaging.
>
>  
>
> When rsyncrypto tries to overwrite a read-only file (which is not 
> possible) it gives me the following error message: "file open failed: 
> Input/output error".
>
>  
>
> Would it be possible/desirable to change this to something like 
> "error: <target file> is read-only" ?
>
>  
>
> Warm regards,
>
>  
>
> Jan
>
Hi Jan,

Can you try it with the attached patch? I greatly enhanced the 
translation between Win32 errors and errno errors, and I believe the 
particular problem should be resolved by it.

Thanks
Shachar

Incompatible changes in the next version of rsyncrypto

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

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.


The second change is only relevant to Windows. I want to make rsyncrypto 
a Unicode built application. On the pluses, this means rsyncrypto will 
be able to handle any file name, no matter what the locale is. However, 
this does require that rsyncrypto use a different format in the filemap 
file (for name encryption) than what is used today. The obvious solution 
is to store this in UTF-16 (which is what Windows uses internally for 
Unicode applications). I see two major problems with this option. The 
first is that this throws out of the window any chance of accessing this 
file from a Unix machine. The second is that there are not that many 
UTF-16 capable editors out there.

A better solution, as far as I'm concerned, is to use UTF-8. This is a 
fairly standard format, and is easily readable by Unix machine by merely 
setting LC_CTYPE to en_US.utf-8 (or any such locale). It is also the 
default locale for most modern Linux distributions. There is just one 
problem - it is very difficult to say, by merely looking at a file, 
whether it is ANSI (the Windows term for non-Unicode) encoded or whether 
it is encoded in UTF-8. This means that upgrade to a new version of 
rsyncrypto would require a manual conversion of the filemap file (I 
will, of course, provide a tool to do that).

I should just point out that this will only affect users of rsyncrypto 
for Windows outside of the USA. If all you use is ASCII for your files, 
then UTF-8 and ANSI produce the same encoding, and you will not see the 
problem.


Another solution, which I am leaning toward, is to add a version number 
to the filemap file. This will allow new versions of rsyncrypto to read 
old version's filemap and use it (but will totally destroy any chance of 
working the other way).

Your input is greatly appreciated.

Thanks,
Shachar

RE: Rsyncrypto maximum file length ?

[Jan A. <jan...@do...>]

I found some additional information regarding NTFS on Windows.

 

http://en.wikipedia.org/wiki/Filename

 

Remarkable that the windows kernel is limiting the NTFS file system.. Must
be some kind of Microsoft marketing decision...

 

  _____  

Van: Jan Alphenaar [mailto:jan...@do...] 
Verzonden: zondag 3 augustus 2008 13:18
Aan: 'L-rsyncrypto'
CC: 'Shachar Shemesh'
Onderwerp: Rsyncrypto maximum file length ?

 

Hi Shachar,

 

I was recently encrypting my Visual Studio files and I ran into an
interesting issue. Rsyncrypto was giving me the following error message:

 

====== BEGIN ERROR MESSAGE ====

file open failed(BackupFiles\D\Jan Alphenaar\Mijn documenten\Backup
1234567\Visu

al
Studio\Backups\20080701-1030\Trouble\0000000000000\11111111111111\bin\OpenSS
L

\perl\5.6\Crypto_SSLeay\blib\lib\Crypt\SSLeay\.svn\text-base\Conn.pm12345678
9.rs

yncrypto_tmp): No such file or directory

======= END ERROR MESSAGE =====

 

My best guess is that the length of the destination file is exceeding the
256 characters. The absolute path for the destination file is, coming
remarkable close to 256 characters.

 

D:\Package 123456789\tmp\BackupFiles\D\Jan Alphenaar\Mijn documenten\Backup
1234567\Visu

al
Studio\Backups\20080701-1030\Trouble\0000000000000\11111111111111\bin\OpenSS
L

\perl\5.6\Crypto_SSLeay\blib\lib\Crypt\SSLeay\.svn\text-base\Conn.pm12345678
9

 

I imagine it is not so easy to set the maximum file length if an application
supports multiple operating systems (and thus multiple file systems). But
would it be possible to generate an error message like "<file name> filename
length to long", or something similar ? If the filename is too long for the
filesystem ?

 

Check out the limits for each filesystem on
http://en.wikipedia.org/wiki/Comparison_of_file_systems

 

As you probably know I am testing on WinXP, and my file system is NTFS.

 

Regards,

 

Jan

Rsyncrypto maximum file length ?

[Jan A. <jan...@do...>]

Hi Shachar,

 

I was recently encrypting my Visual Studio files and I ran into an
interesting issue. Rsyncrypto was giving me the following error message:

 

====== BEGIN ERROR MESSAGE ====

file open failed(BackupFiles\D\Jan Alphenaar\Mijn documenten\Backup
1234567\Visu

al
Studio\Backups\20080701-1030\Trouble\0000000000000\11111111111111\bin\OpenSS
L

\perl\5.6\Crypto_SSLeay\blib\lib\Crypt\SSLeay\.svn\text-base\Conn.pm12345678
9.rs

yncrypto_tmp): No such file or directory

======= END ERROR MESSAGE =====

 

My best guess is that the length of the destination file is exceeding the
256 characters. The absolute path for the destination file is, coming
remarkable close to 256 characters.

 

D:\Package 123456789\tmp\BackupFiles\D\Jan Alphenaar\Mijn documenten\Backup
1234567\Visu

al
Studio\Backups\20080701-1030\Trouble\0000000000000\11111111111111\bin\OpenSS
L

\perl\5.6\Crypto_SSLeay\blib\lib\Crypt\SSLeay\.svn\text-base\Conn.pm12345678
9

 

I imagine it is not so easy to set the maximum file length if an application
supports multiple operating systems (and thus multiple file systems). But
would it be possible to generate an error message like "<file name> filename
length to long", or something similar ? If the filename is too long for the
filesystem ?

 

Check out the limits for each filesystem on
http://en.wikipedia.org/wiki/Comparison_of_file_systems

 

As you probably know I am testing on WinXP, and my file system is NTFS.

 

Regards,

 

Jan

Re: Rsyncrypto running out of disk space

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

Jan Alphenaar wrote:
> Hi,
>
> I am having trouble getting the right version from SVN. I assume I should
> get the files from the trunk folder ?
>
> Jan
>
>   
Yes. What is the trouble?

It might have to do with a scheduled down time sourceforge had for about 
around now. If you are getting timeouts and weird stuff, try again in 12 
hours.

Shachar

RE: Rsyncrypto running out of disk space

[Jan A. <jan...@do...>]

Hi,

I am having trouble getting the right version from SVN. I assume I should
get the files from the trunk folder ?

Jan

-----Oorspronkelijk bericht-----
Van: Shachar Shemesh [mailto:sh...@sh...] 
Verzonden: zondag 27 juli 2008 22:05
Aan: Jan Alphenaar
CC: 'L-rsyncrypto'
Onderwerp: Re: Rsyncrypto running out of disk space

Jan Alphenaar wrote:
>
> Hi again,
>
>  
>
> I have just tested RsynCrypto version 1.12 for this issue (see email 
> below).
>
>  
>
> It is still giving me the error message as below, just wanted to let 
> you know.
>
>  
>
> Regards,
>
>  
>
> Jan
>
>  
>
If you can grab the latest version from SVN, it should now solve this issue.

Shachar

Re: Rsyncrypto running out of disk space

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

Jan Alphenaar wrote:
>
> Hi again,
>
>  
>
> I have just tested RsynCrypto version 1.12 for this issue (see email 
> below).
>
>  
>
> It is still giving me the error message as below, just wanted to let 
> you know.
>
>  
>
> Regards,
>
>  
>
> Jan
>
>  
>
If you can grab the latest version from SVN, it should now solve this issue.

Shachar

RE: File size zero after decrypting with wrong certificate

[Jan A. <jan...@do...>]

Hi again,

 

I have just tested RsynCrypto version 1.12 (on WinXP) for this issue (see
email below). 

 

Rsyncrypto indeed works with a tmp file now. After the error message is
generated, rsyncrypto bails out, leaving my original file intact. But it
also leaves the tmp file on my disc. Would it be possible to delete it ?

 

Another thing I noticed, is that the filename is now removed from the error
message.

 

==== BEGIN OUTPUT =====

D:\Test>"D:\test\RsynCrypto\RsynCrypto.exe" -d
"D:\Test\EncryptedFiles\testfile.pdf" "D:\Test\ClearFiles\testfile.pdf"
"D:\Test\keys\testfile.pdf" "D:\Test\Certificate\Cert.key"

error:0407A079:rsa routines:RSA_padding_check_PKCS1_OAEP:oaep decoding error

===== END OUTPUT ======

 

Thanks in advance.

 

Regards,

 

Jan

 

 

  _____  

Van: Jan Alphenaar [mailto:jan...@do...] 
Verzonden: zaterdag 19 juli 2008 11:44
Aan: 'L-rsyncrypto'
CC: 'Shachar Shemesh'
Onderwerp: File size zero after decrypting with wrong certificate

 

Hi Sachar,

 

Sorry for keeping you busy lately. I now have some kind of theoretical
question.

 

When I encrypt my file with a certificate, let's say certificate A. And I
copy this encrypted file to a CD. Assume I do this on a daily basis. At some
point in time my certificate gets corrupted and I have to generate a new one
(certificate B). This would obviously make my in the past created backups
useless...

 

Now I start creating backups with this new certificate for the next couple
of months, so far so good. Then something happens and I decide to restore
(decrypt) a file from the CD. But - silly me - I use a file which is
encrypted with certificate A, resulting in the following rsyncrypto error.

 

======== BEGIN OUTPUT ========

"D:\Restore\test001.txt" error:0407A079:rsa
routines:RSA_padding_check_PKCS1_OAEP:oaep decoding error:

========= END OUTPUT =========

 

The file which needed to be overwritten was still on my disk before I did
this, but after the decryption my file has size 0, leaving me with nothing.

 

Would it be possible/desirable to make rsyncrypto generate an error message
and leave the file intact when it tries to decrypt a file with the wrong
certificate, in stead of zeroing it out?

 

Warm regards,

 

Jan

 

RE: Rsyncrypto running out of disk space

[Jan A. <jan...@do...>]

Hi again,

 

I have just tested RsynCrypto version 1.12 for this issue (see email below).


 

It is still giving me the error message as below, just wanted to let you
know.

 

Regards,

 

Jan

 

  _____  

Van: Jan Alphenaar [mailto:jan...@do...] 
Verzonden: dinsdag 1 juli 2008 12:46
Aan: 'L-rsyncrypto'
CC: 'Shachar Shemesh'
Onderwerp: Rsyncrypto running out of disk space

 

Hi Shachar,

 

Hopefully you have enjoyed your well deserved holiday.

 

I noticed that rsyncrypto (1.11) gives a rather cryptographic error message
when there is not enough disk space available on the device where the
encrypted file is going to be. During the encryption it bails out on me,
leaving me with a half encrypted (useless) file.

 

For this I have two requests/questions. Would it be possible to make the
error a bit more specific, like "out of disk space" (or something similar).
And what about removing the partially encrypted file when an error occurred
?

 

Here is the output of my encrypted without having enough disk space.

 

=== OUTPUT ===

Z:\tmp>"Z:\rsyncrypto\rsyncrypto.exe" "C:\test test0\3.pst"
"BackupFiles\C\test test0\3.pst" "BackupKeys\C\test test0\3.pst"
"Z:\certificate\cert.crt"

 

This application has requested the Runtime to terminate it in an unusual
way.

Please contact the application's support team for more information.

 

gzip: stdout: Broken pipe

=== OUTPUT ===

 

Warm regards,

 

Jan

 

RE: Rsyncrypto error message

[Jan A. <jan...@do...>]

Sachar,

Nice, it works...

This is the output of the test.

====== BEGIN OUTPUT ======
D:\Test>"D:\test\RsynCrypto\RsynCrypto.exe" D:\Test\ClearFiles\testfile.pdf"
"D:\Test\EncryptedFiles\testfile.pdf" "D:\Test\keys\testfile.pdf"
"D:\Test\Certificate\Cert.crt"
rename failed(D:\Test\EncryptedFiles\testfile.pdf): Permission denied
======= END OUTPUT =======

Thanks !

Regards,

Jan

-----Oorspronkelijk bericht-----
Van: Shachar Shemesh [mailto:sh...@sh...] 
Verzonden: dinsdag 22 juli 2008 7:20
Aan: Jan Alphenaar
CC: 'L-rsyncrypto'
Onderwerp: Re: Rsyncrypto error message

Jan Alphenaar wrote:
>
> Hi Sachar,
>
>  
>
> I have another question regarding error messaging.
>
>  
>
> When rsyncrypto tries to overwrite a read-only file (which is not 
> possible) it gives me the following error message: "file open failed: 
> Input/output error".
>
>  
>
> Would it be possible/desirable to change this to something like 
> "error: <target file> is read-only" ?
>
>  
>
> Warm regards,
>
>  
>
> Jan
>
Hi Jan,

Can you try it with the attached patch? I greatly enhanced the 
translation between Win32 errors and errno errors, and I believe the 
particular problem should be resolved by it.

Thanks
Shachar

Version 1.12 released

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

Hi all,

Version 1.12 fixes the error reporting problem on Windows (or, at least, 
greatly improves the situation). It also employs safe file creation. 
Whenever a file is created, it is created with a temporary name, and 
then renamed over the original. This can be turned off with the new 
--risky-writes command line option.

Share and enjoy
Shachar

Re: File size zero after decrypting with wrong certificate

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

Thomas Constans wrote:
>
> Wouldnot it be better to be warned by rsyncrypto in case we decrypt
> files "in place", overwriting existing ones ?
>
> maybe rsyncrypto should refuse to overwrite existing files, unless a
> --force flag is given ?
>
> I may be able to work on such a patch.
>
>   
I'm  now working on making rsyncrypto use a safe rewrite procedure in 
the best Unix tradition - create a temporary file and then run over the 
original one with a move operation. This will provide atomic replacement 
on Unix and almost atomic on Windows.

Shachar

Re: Rsyncrypto error message

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

Jan Alphenaar wrote:
>
> Hi Sachar,
>
>  
>
> I have another question regarding error messaging.
>
>  
>
> When rsyncrypto tries to overwrite a read-only file (which is not 
> possible) it gives me the following error message: “file open failed: 
> Input/output error”.
>
>  
>
> Would it be possible/desirable to change this to something like 
> “error: <target file> is read-only” ?
>
>  
>
> Warm regards,
>
>  
>
> Jan
>
Hi Jan,

Can you try it with the attached patch? I greatly enhanced the 
translation between Win32 errors and errno errors, and I believe the 
particular problem should be resolved by it.

Thanks
Shachar

Re: File size zero after decrypting with wrong certificate

[Thomas C. <tho...@op...>]

Le Sat, 19 Jul 2008 11:44:20 +0200,
"Jan Alphenaar" <jan...@do...> a écrit :

> 
> The file which needed to be overwritten was still on my disk before I
> did this, but after the decryption my file has size 0, leaving me
> with nothing.


Wouldnot it be better to be warned by rsyncrypto in case we decrypt
files "in place", overwriting existing ones ?

maybe rsyncrypto should refuse to overwrite existing files, unless a
--force flag is given ?

I may be able to work on such a patch.

Regards


-- 
Thomas Constans
openDoor
06 23 37 87 85
09 71 73 91 75

File size zero after decrypting with wrong certificate

[Jan A. <jan...@do...>]

Hi Sachar,

 

Sorry for keeping you busy lately. I now have some kind of theoretical
question.

 

When I encrypt my file with a certificate, let's say certificate A. And I
copy this encrypted file to a CD. Assume I do this on a daily basis. At some
point in time my certificate gets corrupted and I have to generate a new one
(certificate B). This would obviously make my in the past created backups
useless...

 

Now I start creating backups with this new certificate for the next couple
of months, so far so good. Then something happens and I decide to restore
(decrypt) a file from the CD. But - silly me - I use a file which is
encrypted with certificate A, resulting in the following rsyncrypto error.

 

======== BEGIN OUTPUT ========

"D:\Restore\test001.txt" error:0407A079:rsa
routines:RSA_padding_check_PKCS1_OAEP:oaep decoding error:

========= END OUTPUT =========

 

The file which needed to be overwritten was still on my disk before I did
this, but after the decryption my file has size 0, leaving me with nothing.

 

Would it be possible/desirable to make rsyncrypto generate an error message
and leave the file intact when it tries to decrypt a file with the wrong
certificate, in stead of zeroing it out?

 

Warm regards,

 

Jan

 

Re: Rsyncrypto error message

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

Jan Alphenaar wrote:
>
> Hi Sachar,
>
>  
>
> I have another question regarding error messaging.
>
>  
>
> When rsyncrypto tries to overwrite a read-only file (which is not 
> possible) it gives me the following error message: “file open failed: 
> Input/output error”.
>
>  
>
That's not what I get (Linux):
> Decrypting a.enc/a/b/2
> Decrypting a.dec/a/b/2 error: file open failed(a.dec/a/b/2): 
> Permission denied
Can you give me precise steps to recreate the problems?

Shachar

Re: Rsyncrypto error message

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

Jan Alphenaar wrote:
>
>  
>
> Would it be possible/desirable to change this to something like 
> “error: <target file> is read-only” ?
>
Hi Jan,

I won't have time in the immediate future to have a look at it, but in 
principle, these error messages are reported by the OS. As such, it will 
not be easily possible to change them.

It is possible, however, that in the scenario you describe the error is 
not reported at the right time, and this is the cause of the wrong error 
message. If that is the case, it may be possible to have rsyncrypto 
produce the correct error message.
>
>  
>
> Warm regards,
>
>  
>
> Jan
>
Shachar

Re: question about the manual

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

Frederico Rodrigues Abraham wrote:
> The modification time will never be the same, since the 
> encryption/decryption is possibly done much after the source file has 
> changed.
>   
rsyncrypto sets the encrypted file time to that of the source file, so, 
no, it should not be different.

Shachar

question about the manual

[Frederico R. A. <dev...@gm...>]

I have a question:

---------------
       -c, --changed
              Check the src and destination modified time (see 
--modify-window) prior to performing the operation. If the modified time 
is the same, assume that the files  are
              also  the  same,  and  skip  the operation. Notice that 
unlike rsync, file sizes are not compared. This is because the file size 
is expected to change during the
              encryption (and thus decryption) operation.

---------------

Shouldn't this be 'check if source is newer than destination using the 
file modification time' ?
The modification time will never be the same, since the 
encryption/decryption is possibly done much after the source file has 
changed.

Thank you,
-- Fred

Rsyncrypto error message

[Jan A. <jan...@do...>]

Hi Sachar,

 

I have another question regarding error messaging.

 

When rsyncrypto tries to overwrite a read-only file (which is not possible)
it gives me the following error message: "file open failed: Input/output
error".

 

Would it be possible/desirable to change this to something like "error:
<target file> is read-only" ?

 

Warm regards,

 

Jan

Rsyncrypto running out of disk space

[Jan A. <jan...@do...>]

Hi Shachar,

 

Hopefully you have enjoyed your well deserved holiday.

 

I noticed that rsyncrypto (1.11) gives a rather cryptographic error message
when there is not enough disk space available on the device where the
encrypted file is going to be. During the encryption it bails out on me,
leaving me with a half encrypted (useless) file.

 

For this I have two requests/questions. Would it be possible to make the
error a bit more specific, like "out of disk space" (or something similar).
And what about removing the partially encrypted file when an error occurred
?

 

Here is the output of my encrypted without having enough disk space.

 

=== OUTPUT ===

Z:\tmp>"Z:\rsyncrypto\rsyncrypto.exe" "C:\test test0\3.pst"
"BackupFiles\C\test test0\3.pst" "BackupKeys\C\test test0\3.pst"
"Z:\certificate\cert.crt"

 

This application has requested the Runtime to terminate it in an unusual
way.

Please contact the application's support team for more information.

 

gzip: stdout: Broken pipe

=== OUTPUT ===

 

Warm regards,

 

Jan

 

Re: Version 1.11 released

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

For the record: Version 1.11 .msi installer works fine and I tested the "do
not abort on error" feature with a couple of test cases (open files, illegal
filenames), and it works as expected.

However: for anyone who (for some strange reason like my own) wants to get
out of "DLL hell", I have what is essentially version 1.11 compiling with
VS8.



2008/6/27 Julian <jul...@gm...>:

> Yep, the problem seems to be with something called WinSxS (side by side)
> that's handled by the msi. (it looks horrible).
>
> Any chance of making available the compiled exe before it is bundled into
> the msi? It should work like that I guess.. I think it would make things
> much simpler with my setup.
>
> Thanks
> Julian
>
> 2008/6/26 Shachar Shemesh <sh...@sh...>:
>
> Julian wrote:
>>
>>> Hi Shachar.. hope I'm not disturbing your vacation... if so, you may
>>> ignore this until you return, as it is not really urgent!
>>>
>> Allow me to reassure you that, urgent or not, I would never interrupt my
>> vacation for such a thing. That's why it's called "vacation".
>>
>>>
>>> Anyway I noticed that on Windows:
>>> if I copy the new rsyncrypto.exe file (V1.11) into a directory with all
>>> my scripts etc..(without installing the msi) I get a "The system cannot
>>> execute the specified program" error at the command line.
>>>
>>> A quick google search shows that this is generally a DLL problem.. I
>>> noticed the argtable2.dll is newer than previous versions (and smaller in
>>> size), but copying this over does not fix the problem.
>>>
>>> What does fix the problem is installing the msi into "Program
>>> Files\Rsyncrypto"...
>>> now the "other" exe now begins to work from the original place...
>>> Uninstall the msi and the problem returns.
>>>
>>> For information purposes, can you inform me of the exact dependencies of
>>> the "rsyncrypto.exe" program to run?
>>> Apologies if this has been implied from the previous posts about
>>> upgrading to the new Visual Studio etc...
>>>
>> One of the great tragedies of the way Visual Studio is increasingly
>> behaving is that it doesn't matter whether you wrote the program or not. You
>> still don't understand its requirements. Visual Studio calculates them
>> automatically for you and leaves you out of the picture.
>>
>> I don't know why it didn't work for you. Maybe some internal MSI
>> dependencies, maybe something else. Whatever it is, I have given up fighting
>> it.
>>
>> Shachar
>>
>
>

Re: Version 1.11 released

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

Yep, the problem seems to be with something called WinSxS (side by side)
that's handled by the msi. (it looks horrible).

Any chance of making available the compiled exe before it is bundled into
the msi? It should work like that I guess.. I think it would make things
much simpler with my setup.

Thanks
Julian

2008/6/26 Shachar Shemesh <sh...@sh...>:

> Julian wrote:
>
>> Hi Shachar.. hope I'm not disturbing your vacation... if so, you may
>> ignore this until you return, as it is not really urgent!
>>
> Allow me to reassure you that, urgent or not, I would never interrupt my
> vacation for such a thing. That's why it's called "vacation".
>
>>
>> Anyway I noticed that on Windows:
>> if I copy the new rsyncrypto.exe file (V1.11) into a directory with all my
>> scripts etc..(without installing the msi) I get a "The system cannot execute
>> the specified program" error at the command line.
>>
>> A quick google search shows that this is generally a DLL problem.. I
>> noticed the argtable2.dll is newer than previous versions (and smaller in
>> size), but copying this over does not fix the problem.
>>
>> What does fix the problem is installing the msi into "Program
>> Files\Rsyncrypto"...
>> now the "other" exe now begins to work from the original place...
>> Uninstall the msi and the problem returns.
>>
>> For information purposes, can you inform me of the exact dependencies of
>> the "rsyncrypto.exe" program to run?
>> Apologies if this has been implied from the previous posts about upgrading
>> to the new Visual Studio etc...
>>
> One of the great tragedies of the way Visual Studio is increasingly
> behaving is that it doesn't matter whether you wrote the program or not. You
> still don't understand its requirements. Visual Studio calculates them
> automatically for you and leaves you out of the picture.
>
> I don't know why it didn't work for you. Maybe some internal MSI
> dependencies, maybe something else. Whatever it is, I have given up fighting
> it.
>
> Shachar
>

Re: Version 1.11 released

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

Julian wrote:
> Hi Shachar.. hope I'm not disturbing your vacation... if so, you may 
> ignore this until you return, as it is not really urgent!
Allow me to reassure you that, urgent or not, I would never interrupt my 
vacation for such a thing. That's why it's called "vacation".
>
> Anyway I noticed that on Windows:
> if I copy the new rsyncrypto.exe file (V1.11) into a directory with 
> all my scripts etc..(without installing the msi) I get a "The system 
> cannot execute the specified program" error at the command line.
>
> A quick google search shows that this is generally a DLL problem.. I 
> noticed the argtable2.dll is newer than previous versions (and smaller 
> in size), but copying this over does not fix the problem.
>
> What does fix the problem is installing the msi into "Program 
> Files\Rsyncrypto"...
> now the "other" exe now begins to work from the original place... 
> Uninstall the msi and the problem returns.
>
> For information purposes, can you inform me of the exact dependencies 
> of the "rsyncrypto.exe" program to run?
> Apologies if this has been implied from the previous posts about 
> upgrading to the new Visual Studio etc...
One of the great tragedies of the way Visual Studio is increasingly 
behaving is that it doesn't matter whether you wrote the program or not. 
You still don't understand its requirements. Visual Studio calculates 
them automatically for you and leaves you out of the picture.

I don't know why it didn't work for you. Maybe some internal MSI 
dependencies, maybe something else. Whatever it is, I have given up 
fighting it.

Shachar