On Fri, May 09, 2008 at 07:55:23AM +0300, Shachar Shemesh wrote:
> > The resulting encrypted file name is not listed at any point, and
> > rsyncrypto chokes on five -v.
> >
> > This is 1.07, by the way.
>
> Got your point. Would adding an additional level of verbosity that
> outputs the encrypted n
Robin Lee Powell wrote:
> Shachar asked me to move this to the list; you'll have to read
> bottom-up, I'm afraid.
>
Which is why I asked that further discussion take place on the list :-)
> No, rsyncrypto most certainly does not do this with any number of
> -v:
>
> $ rsyncrypto - --trim=1 --
Robin Lee Powell wrote:
> So I used a special BackupPC script to generate a tarball of hard
> link listings only. I took about 2 hours, and came to 1.1GiB. Then
> I ran rsyncrypto against it. It took 2 minutes, and came back with
> a 92MiB file. I'm like "Oh no, another bug."
>
> Nope; I decryp
So I used a special BackupPC script to generate a tarball of hard
link listings only. I took about 2 hours, and came to 1.1GiB. Then
I ran rsyncrypto against it. It took 2 minutes, and came back with
a 92MiB file. I'm like "Oh no, another bug."
Nope; I decrypted it, and it md5sum matches. Th
On Thu, May 08, 2008 at 02:04:22PM -0700, Robin Lee Powell wrote:
> $ rsyncrypto --trim=1 --ne-nesting=5 --name-encrypt=filemap --delete -c -v -r
> a a.enc a.keys backup.crt
> Delete 5974EC4026990DE16FAD43681769DC72 (b/c/bar)
> $ find a.enc -name 5974EC4026990DE16FAD43681769DC72 -ls
> 12359639
On Mon, May 05, 2008 at 03:15:46PM +0300, Shachar Shemesh wrote:
>
> Hi Robin,
>
> Robin Lee Powell wrote:
> > rsyncrypto is *so* awesome; if only it didn't hate me. :(
> >
> > $ find a.enc/ -name 5974EC4026990DE16FAD43681769DC72 -ls
> > 123596394 -rw-r--r-- 1 rlpowell users 244 Fe
Shachar asked me to move this to the list; you'll have to read
bottom-up, I'm afraid.
No, rsyncrypto most certainly does not do this with any number of
-v:
$ rsyncrypto - --trim=1 --ne-nesting=5 --name-encrypt=filemap --delete -c
-v -r a a.enc a.keys backup.crt
Skipping unchanged file a/b/d/
Hi Shachar,
Your latest version of the MSI package is not generating the error
"rsyncrypto.exe - Unable To Locate Component" anymore. So it looks like your
work around is working correctly.
Unfortunately I still have my original error message in my test scenario as
reported a couple of months ago
Randy Perkins wrote:
> Hello
> Thanks for the program. Keep up the good work.
> If I had one request, it would be to see some third party testing on how
> robust the encryption is , particularly if someone at the remote end
> could save the daily changes of a given encrypted file and use the
> cha
Hello
Thanks for the program. Keep up the good work.
If I had one request, it would be to see some third party testing on how
robust the encryption is , particularly if someone at the remote end
could save the daily changes of a given encrypted file and use the
changes to extract the unencrypted f
10 matches
Mail list logo