Sunday, 21 March 2010
And yet another mod_dav_svn idea -- sort of
I refrain from having subversion repositories for my personal documents on a public ("root") server. I rather keep them in repositories on my home network. I don't like the idea of a (constantly exposed) internet-server containing all my documents. That's why there should be a second line of defense in case such a system is hacked. The "obvious" solution would be to use a cryptographic filesystem on the server that has to be mounted before the repository is accessed. However, that approach introduces a whole slew of technical issues (only root can/should mount, has to be manually dismounted, ...). Why not instead implement a new (or extend an existing) SVN backend that provides such cryptographic capabilities? Unfortunately, it looks like this can't be implemented as a source code patch (instead of a plug-in or extension).
On a side note: I recently stumbled across this SQL backend for Subversion (sadly it hasn't been continued and looks incompatible with current releases).
[Trackback URL for this entry]
