On Wed, Oct 27, 2010 at 10:46, Andreas Houben
> as you maybe have already noticed, I'm trying to build my own tortoise
> project from the trunk source code. The background is, that I'm
> participating in a university project at the Ruhr Universität Bochum.
> The goal of this project is to develop a tortoise version, that is
> able to encrypt files before uploading to a SVN server. We are well
> aware of the fact that you can't diff encrypted files and we are
> therefore ruining one of the main features of subversion. But our
> supervising tutor wants to use that system to store binaries, where
> diff doesn't make sense anyway. The cause of the encryption is to
> protect those binaries, in case the subversion server gets compromised
> by a hostile party. The main question in this project will be how to
> distribute the keys for the en-/decryption. But that's just some
> background information on myself.
> Actually I am setting up a debug environment in a virtual machine to
> distribute to my colleagues. Our first goal is to understand the code.
> Therefore I'm asking you if there are any documents that help us
> achieving that goal. I already found the trunk\doc\source\hacking.txt,
> but as far as I can see, that document only explains how to hack the
> Do you have any tips or advice on where to start analysing the
> sourcecode? That would be great.
You could run doxygen on the sourcecode:
$ nant APIDocs
will generate a nice chm file with our API docs.
But: why do you need to hack TSVN to achieve your goal? Would it be
easier to just implement your own custom "diff" tool that in your case
doesn't do a diff but encrypts/decrypts the files?
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-10-27 11:31:19 CEST