Some C help patching sender.c (from:plain source -> encrypted
destination: rsync + gpg)
ml at nzl.com.ar
Mon Jul 7 21:42:04 EST 2003
I am exploring extending Kyle Jones' patch (which implements
post-transfer filter in receiver.c) to pre-filter or otherwise
pre-process the file before it is sent.
Kyle Jones patch can be found here
and the rationale for what I am trying to do here
Down to what I am asking help with: I am _not_ a C hacker at all, my
strenghts are Perl -- if anywhere at all. So I would appreciate your
advise before I shoot myself in the foot.
Thanks for your patience.
I have studied the sources and gotten down to sender.c (cvs 1.17), in
particular the line where it calls do_open() and I am intending to
create do_popen as an alternative to do_open() (in syscall.c).
I have seen Kyle's approach of handling the forking directly, and I know
I cannot handle that level of complexity. Using something like popen (I
reference) I can probably get away with.
One of my concerns is that even though we are setting --whole-file, when
I follow the program logic and the output of test runs with -vvv it is
still computing CRCs and (at least seems to be) preparing deltas.
Hmmm, re-reading it now it seems that the do_open() I am thinking of is
in an if(!read_batch) block and the CRC/deltas are under if(read_batch).
Is read_batch always true when using --whole-files? Seems to be.
Second concern: where is the reading and transmission of th file
happening? If the do_open is in line 183, where's the read/transmit,
map_file() line 202 puts the data uin buf, and then, what? You see,
write_int doesn't use buf.
And where is the handle closed?
Thanks for any tips here...
More information about the rsync