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

Re: Selecting encrypted files list

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

Gary Holzer wrote:

>Hi Shachar,
>
>Thanks for the reply. I actually did a work around bu writing to
>/usr/local/bin rather than cygdrive/c, this worked fine. When I tried
>to write to cygdrive I couldnt get it to encrypt or create the folder
>structures due to the permission error.
>
>I am running cygwin as there doesnt seem to be a windows version of
>rsync i.e. I run rsycrypto first then rsync these files.
>  
>
What I do is install rsync + the one or two cygwin dlls it require. I 
then run it as if it's a standard windows command line (thought I of 
course have to translate the actual parameters to unix-type paths). 
Cygwin is fairly self-configuring, and even if it was not installed on 
the machine, it works as is.

>Cheers
>
>Gary
>  
>
       Shachar

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

Re: Selecting encrypted files list

[Gary H. <gar...@gm...>]

Hi Shachar,

Thanks for the reply. I actually did a work around bu writing to
/usr/local/bin rather than cygdrive/c, this worked fine. When I tried
to write to cygdrive I couldnt get it to encrypt or create the folder
structures due to the permission error.

I am running cygwin as there doesnt seem to be a windows version of
rsync i.e. I run rsycrypto first then rsync these files.

Cheers

Gary



On 7/3/05, Shachar Shemesh <rsy...@sh...> wrote:
> Gary Holzer wrote:
>=20
> >Dear List,
> >
> >
> >
> Hi Gary,
>=20
> Sorry for taking so long to answer. I have totally missed your email.
>=20
> >In a previous part of the script I sucessfully create the $FILELIST
> >and set up the other variables. The $CRYPT_DIR is on the same box that
> >is running cygwin i.e. the script and rsyncrypto. For some reason when
> >I run the script I get the following errors in the $TEMPFILE for each
> >file I try to encrypt in $FILELIST
> >
> >e.g.
> >
> >Error in encryption of /cygdrive/c/Work/Jo/Uni/Proposal - professional
> >comm.doc: mkdir failed(/cygdrive/c): Permission denied
> >
> >
> Did the actual encryption succeed?
>=20
> The problem is that rsyncrypto, in order to make sure the entire
> directory path exists, creates each individual subdirectory. As such, it
> also tries to create /cygdrive and /cygdrive/c. It is programmed to
> ignore "file exists" errors as irrelevant.
>=20
> The problem is that /cygdrive and /cygdrive/c are not regular
> directories. They are made up by cygwin for the purpose of emulating the
> Windows forset view over the cygwin tree view. As such, cygwin returns
> "permission denited" for them, rather than the more conventional "file
> exists". I actually think this is a bug in cygwin, btw.
>=20
> I have a question, though. Why are you using the cygwin version when you
> can use the native Windows version?
>=20
>        Shachar
>=20
> --
> Shachar Shemesh
> Lingnu Open Systems Consulting
> http://www.lingnu.com/
>=20
>

Re: Selecting encrypted files list

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

Gary Holzer wrote:

>Dear List,
>
>  
>
Hi Gary,

Sorry for taking so long to answer. I have totally missed your email.

>In a previous part of the script I sucessfully create the $FILELIST
>and set up the other variables. The $CRYPT_DIR is on the same box that
>is running cygwin i.e. the script and rsyncrypto. For some reason when
>I run the script I get the following errors in the $TEMPFILE for each
>file I try to encrypt in $FILELIST
>
>e.g.
>
>Error in encryption of /cygdrive/c/Work/Jo/Uni/Proposal - professional
>comm.doc: mkdir failed(/cygdrive/c): Permission denied
>  
>
Did the actual encryption succeed?

The problem is that rsyncrypto, in order to make sure the entire 
directory path exists, creates each individual subdirectory. As such, it 
also tries to create /cygdrive and /cygdrive/c. It is programmed to 
ignore "file exists" errors as irrelevant.

The problem is that /cygdrive and /cygdrive/c are not regular 
directories. They are made up by cygwin for the purpose of emulating the 
Windows forset view over the cygwin tree view. As such, cygwin returns 
"permission denited" for them, rather than the more conventional "file 
exists". I actually think this is a bug in cygwin, btw.

I have a question, though. Why are you using the cygwin version when you 
can use the native Windows version?

       Shachar

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

Re: Selecting encrypted files list

[Gary H. <gar...@gm...>]

Dear List,

I am setting up the win32 version of rsyncrypto to run under cygwin
from a XP box using the following command;

$RSYNC_CRYPTO -c --gzip $GZIP --filelist $FILELIST \
    $CRYPT_DIR $KEYS_DIR $CERT > $TEMPFILE 2>&1

In a previous part of the script I sucessfully create the $FILELIST
and set up the other variables. The $CRYPT_DIR is on the same box that
is running cygwin i.e. the script and rsyncrypto. For some reason when
I run the script I get the following errors in the $TEMPFILE for each
file I try to encrypt in $FILELIST

e.g.

Error in encryption of /cygdrive/c/Work/Jo/Uni/Proposal - professional
comm.doc: mkdir failed(/cygdrive/c): Permission denied

I can succefully manually create directories from within cygwin. I
have used chown and chmod as well cacls in Windows to ensure that I
have permissions. Only thing I can figure is that rsyncrypto is having
an issue in creating folders? I have managed to get this whole thing
working on some work boxes (albeit using W2K).

Help please, as I have spent a fair few hours to no avail.

Gary

PS - using the version of gzip that comes with the windows version of
rsyncrypto (which I am also using)

Re: Selecting encrypted files list

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

am...@am... wrote:

>On 6/8/05, Shachar Shemesh
><rsy...@am...> wrote:
>  
>
>>The first thing that comes to mind is:
>>find . -name \*.dbf -or -name \*.fpt -or -name \*.cdx -maxdepth 1 -print
>>| rsyncrypto --filelist - destinationdir keysdir certificate.crt
>>    
>>
>
>While you are at it, would you add an option to rsyncrypto to accept
>null-separated file lists? (a-la find's "-print0" and xargs' "-0")
>
>Cheers,
>
>--Amos
>
>
>  
>
File it in the tracker?

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

Re: Selecting encrypted files list

[<am...@am...>]

On 6/8/05, Shachar Shemesh
<rsy...@am...> wrote:
> The first thing that comes to mind is:
> find . -name \*.dbf -or -name \*.fpt -or -name \*.cdx -maxdepth 1 -print
> | rsyncrypto --filelist - destinationdir keysdir certificate.crt

While you are at it, would you add an option to rsyncrypto to accept
null-separated file lists? (a-la find's "-print0" and xargs' "-0")

Cheers,

--Amos

Selecting encrypted files list

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

Gary Holzer wrote:

>Dear List,
>
>I am currently trying to setup rsyncrypto so that the it will only
>encrypt certain file types e.g. *.dbf *.fpt *.cdx and also not to
>recursively look through a folder structure. The -r seems to include
>all directories recursively. Could I use the --trim?
>
>I am currently unsucessfuly playing around with building a file list
>in a text file and parsing this to rsyncrypto.
>
>Any help would be much appreciated.
>
>Thanks
>
>Gary
>  
>
The first thing that comes to mind is:
find . -name \*.dbf -or -name \*.fpt -or -name \*.cdx -maxdepth 1 -print 
| rsyncrypto --filelist - destinationdir keysdir certificate.crt

There may be some room for tweaking this, of course. For example, the 
above will not delete encrypted files from the encrypted dir. If that is 
what you want, a more elaborate scheme will need to be performed.

Hope this helps,
          Shachar

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

Re: AES keys

[Gary H. <gar...@gm...>]

Dear List,

I am currently trying to setup rsyncrypto so that the it will only
encrypt certain file types e.g. *.dbf *.fpt *.cdx and also not to
recursively look through a folder structure. The -r seems to include
all directories recursively. Could I use the --trim?

I am currently unsucessfuly playing around with building a file list
in a text file and parsing this to rsyncrypto.

Any help would be much appreciated.

Thanks

Gary

Re: Windows Rsyncrypto

[Joost v. d. B. <jo...@se...>]

I can confirm i've got the same problem. This file seems to be part of 
OpenSSL. But unfortunately after installing OpenSSL for windows, I still get 
an error message: "The ordinal 3024 could not be located in the dynamic links 
library LIBEAY32.dll."

So this file should be included with the package.

- Joost

On Tuesday 24 May 2005 16:50, Donald Orbin wrote:
> Another congrts from me on this rsync friendly crypto
> app.
>
> Unfortunately my oBSD box is out of commission for a
> while, so I downloaded the recently released windows
> verion of Rsyncrypto.
>
> I ran it from the command line and received an error
> that : :dynamic link library LIBEAY32.dll could not be
> found in the specified path"
>
> Hope I'm not missing something here - but would
> appreciate any pointers from someone who has this
> running on win32.
>
> Thanx all
> Don

Windows Rsyncrypto

[Donald O. <orb...@ya...>]

Another congrts from me on this rsync friendly crypto
app.

Unfortunately my oBSD box is out of commission for a
while, so I downloaded the recently released windows
verion of Rsyncrypto.

I ran it from the command line and received an error
that : :dynamic link library LIBEAY32.dll could not be
found in the specified path"

Hope I'm not missing something here - but would
appreciate any pointers from someone who has this
running on win32.

Thanx all
Don 


		
___________________________________________________________ 
How much free photo storage do you get? Store your holiday 
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com

Re: AES keys

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

Gary Holzer wrote:

>Hi All,
>
>I am about to install a test rsyncrypto best, the only thing I am not
>sure of is how to create a single AES key (certificate)? Any pointers
>would be much appreciated.
>  
>
AES keys (a.k.a. symmetric keys) are generated automatically by 
rsyncrypto per encrypted files. This is what is stored in the "key" file 
name you specify as the third parameter. What you are likely asking 
about is generating the PKCS X509 certificate, which is an RSA key 
(asymmetric key), which is the fourth parameter.

The rsyncrypto manual points you to the req(1) and x509(1) manual pages 
of openssl. Off the top of my head, the command line to generate would 
probably be something like:
openssl req -new -nodes -x509 -out backup.crt -keyout backup.key

The *.crt file is the certificate (public key) file. rsyncrypto ignores 
just about all fields of the resulting certificate except the actual 
key. This file is not secret. This file can be used for backup 
(encryption), as well as restore (decryption) assuming you have not lost 
the symmetric key files mentioned above (hot restore).

If the symmetric keys were lost, you will need the *.key RSA key 
(private key), which must therefor be kept totally safe and secret, or 
the entire encryption is worthless.

Repeating for briefty's sake:
- Each file is encrypted using AES. Each file gets its own key (called 
the symmetric key). This is stored in a file given as the third 
parameter to rsyncrypto, and should not be backed up. Each file should 
be 68 bytes long. This file can be used, along with the public key, to 
perform a restore (assuming you still have it).
- This file is also encrypted inside the encrypted file that should be 
backed up. It is encrypted using the asymmetric key, or the RSA key. 
This key should be specifically generated by you, using the command line 
above.
- The *.key file is the secret part of the key, and should be kept, 
well, secret. It is only ever needed by rsyncrypto if you need to 
perform a restore after the key files were lost.
- The *.crt file is the public key. It is the key rsyncrypto should be 
usually given as its fourth parameter, for both encryption and 
decryption with key file present.

I hope this makes things a little clearer.

       Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

AES keys

[Gary H. <gar...@gm...>]

Hi All,

I am about to install a test rsyncrypto best, the only thing I am not
sure of is how to create a single AES key (certificate)? Any pointers
would be much appreciated.

Thanks

Gary

Version 0.14 released

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

New to this version:
If you are on Linux:
1. Rsyncrypto now requires "argtable" in order to compile or run.
2. Argument processing in case of incorrect argument usage now causes 
segmentation fault
3. There are no new features or bug fixes.
4. Due to the libargtable dependency, the Debian repository will not 
carry this (or any other newer) version of rsyncrypto until we manage to 
get argtable in. Getting rsyncrypto in took about a month from the point 
it was uploaded to the point it was approved. There is no reason to 
believe argtable will take any less.

However.....
If you are on Windows:
There is now a windows version of rsyncrypto!!!!!!

We will hope to fix most other regressions, as well as make 
improvements, in the near future (i.e. - before argtable is approved for 
Debian :-).

Please send all bug reports and questions to the usual place (i.e. - 
this list).

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

Windows branch in CVS

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

Hi all,

If anyone is interested, CVS now has a branch called "B_WIN32_PORT". It 
is a work in progress of making rsyncrypto compile on Windows using 
Visual Studio. Feel free to check it out.

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

Version 0.13 released

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

Hi all,

Version 0.13 of rsyncrypto has just been released. Main changes are:
- Rsyncrypto now works on OpenBSD (assuming you have a patched gzip, but..)
- The patch for gzip to make it work with rsyncrypto (--rsyncable) is 
now included in the "contrib" folder of the source.
- Some minor clarification for my position on the "OpenSSL GPL 
exception" problem. The exception is still there, as I do not intend to 
make anyone's life harder. Read the "COPYING" file for more details.

As for future directions - I am now working on making rsyncrypto work on 
more platforms, and in particular, Windows. The first stage for 
achieving this is moving away from "getopt_long" as a command line 
processing mechanism. I have found "argtable" 
(http://argtable.sourceforge.net), and am migrating rsyncrypto there. 
Expect a new version soon. This alone should allow us to use rsyncrypto 
on other Unixes, such as solaris.

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

OpenBSD fix committed

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

Hi all,

I just committed a fix to a problem that prevented rsyncrypto from 
working on OpenBSD. Apparently, either Linux or BSD has a somewhat 
strange behavior where mmap is used with PROT_WRITE but not PROT_READ. 
On BSD you can't do anything with the memory in question, while on Linux 
you can.

This is a first step toward porting rsyncrypto to Windows, making it 
totally multi-platform.

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

Re: Run rsyncrypto on windows

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

DavidV wrote:

>Message body follows:
>
>Shachar,
>
>This project is very interesting.
>I think you are the only programmer working on a crypto
>program compatible with rsync and I want to congratulate you
>for that.
>  
>
Thanks. After having written it already it turns out there were other 
attempts as well. Both other technologies that I have seen seem to 
require you to keep around your entire previously synced copy, however, 
and so seem to me much less practical than rsyncrypto, which only 
requires you to keep around a ~64 bytes state file per encrypted file. 
As I have not actually worked with any of them, however, I cannot tell 
you that for sure. I'm ccing the mailing list in case someone else has 
any better experience to share.

>But I have an important question for you :
>Is it possible to run it on windows ?
>  
>
Possible, yes, I guess so.

>If so, how ?
>  
>
You need to port it.

Porting rsyncrypto to Windows IS on my "to do" list, so I will get 
around to it eventually, but I really can't tell you when that will 
happen. There are two major hurdles to clear. One is that only Debian  
GNU/{Linux, Hurd, FreeBSD} currently ship gzip with the rsyncable patch 
by default, which means that on any other platform you will have to 
compile gzip as well as rsyncrypto in order to use it. The idea is to 
replace gzip with zlib, and keep a local copy already patched, to be 
compiled along with rsyncrypto. That is the first hurdle to pass.

The second hurdle to pass is to switch rsyncrypto to using standard IO, 
or at least use wrappers. This is not a big problem, as it sort of uses 
wrappers already. It's just something I'll have to do sometimes soon. 
There is also the question of Unicode, but that's more of a rsync issue 
than a rsyncrypto issue.

>Thank you very much in advance for taking a few minutes of
>your precious time to reply.
>  
>
No problem, but please direct all future requests to the mailing list.

>DavidV.
>  
>
          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

Version 0.12 released

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

Version 0.12 has just been released. Among the changes is a solution to 
bug 1161308 (change the --delete option meaning), clarification of the 
license regarding linking with OpenSSL, and a minor bug fix regarding 
directory creation and absolute paths.

The version is of "beta" status, and can be downloaded from 
http://sourceforge.net/project/showfiles.php?group_id=129038&package_id=141365&release_id=315881.

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html

Welcome

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

Announcing the new mailing list for support, discussions and 
announcements on all things rsyncrypto related.

          Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html