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
> > 12359639    4 -rw-r--r--   1 rlpowell users         244 Feb 21 10:03 
> > a.enc/5/59/597/5974/5974E/5974EC4026990DE16FAD43681769DC72
> >
> > $ 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    4 -rw-r--r--   1 rlpowell users         244 Feb 21 10:03 
> > a.enc/5/59/597/5974/5974E/5974EC4026990DE16FAD43681769DC72
> >
> > $ bash -c "cat filemap | tr '\000' '\012'"
> >   
> I use "tr '\0' '\n'" myself.
> > /1314AF0918C5FA40C1CBB763CF9BFD3D b/c/frobnitz
> > /5974EC4026990DE16FAD43681769DC72 b/c/bar
> > /D537DB78571FBCF53B9417A3A5B47FF5 b/d/foo
> >
> > So the output says the file was deleted, but it in fact was deleted
> > from neither the *encrypted space* nor the filemap.
> >   
> Are you sure about the encrypted space part of that claim? Nothing
> in the output you showed here suggests that the actual encrypted
> file was not deleted.

Umm.  It most certainly does.

Encrypted file before:

> > $ find a.enc/ -name 5974EC4026990DE16FAD43681769DC72 -ls
> > 12359639    4 -rw-r--r--   1 rlpowell users         244 Feb 21 10:03 
> > a.enc/5/59/597/5974/5974E/5974EC4026990DE16FAD43681769DC72

Deletion:

> > $ 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)

Encrypted file after:

> > $ find a.enc/ -name 5974EC4026990DE16FAD43681769DC72 -ls
> > 12359639    4 -rw-r--r--   1 rlpowell users         244 Feb 21 10:03 
> > a.enc/5/59/597/5974/5974E/5974EC4026990DE16FAD43681769DC72

> Unless you also specify "--delete-keys", not deleting the key and file 
> mapping is what rsyncrypto is supposed to do. 

I'm talking about the encrypted file, not the key and file mapping.

> If the above explanation does not appear to explain the symptoms
> you describe (I know it's been a while, but if you can recheck it
> would be great), then please do check out the head of SVN and test
> again. If the problem is still not solved, please let me know.

$ 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    4 -rw-r--r--   1 rlpowell users         244 Feb 21 10:03 
a.enc/5/59/597/5974/5974E/5974EC4026990DE16FAD43681769DC72

And I can do it again:

$ 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    4 -rw-r--r--   1 rlpowell users         244 Feb 21 10:03 
a.enc/5/59/597/5974/5974E/5974EC4026990DE16FAD43681769DC72

No matter how many times I do it, it keeps claiming to delete
5974EC4026990DE16FAD43681769DC72, but keeps failing to do so.

--delete-keys *does*, in fact, delete the file mapping, but leaves the
encrypted file:

$ rsyncrypto --delete-keys --trim=1 --ne-nesting=5 --name-encrypt=filemap 
--delete -c -v -r a a.enc a.keys backup.crt
Delete 5974EC4026990DE16FAD43681769DC72 (b/c/bar)
Delete key 5974EC4026990DE16FAD43681769DC72 (b/c/bar)
$ find a.enc -name 5974EC4026990DE16FAD43681769DC72 -ls 
12359639    4 -rw-r--r--   1 rlpowell users         244 Feb 21 10:03 
a.enc/5/59/597/5974/5974E/5974EC4026990DE16FAD43681769DC72
$ cat filemap| tr '\0' '\n'
/1314AF0918C5FA40C1CBB763CF9BFD3D b/c/frobnitz
/D537DB78571FBCF53B9417A3A5B47FF5 b/d/foo

-Robin

-- 
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Rsyncrypto-devel mailing list
Rsyncrypto-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsyncrypto-devel

Reply via email to