Re: feature request: encrypt before commit, decrypt after update

On Tue, Oct 14, 2008 at 10:17 AM, Milen A. Radev <milen_at_radev.net> wrote:
[...]
> AFAICT that could be done with some client-side hooks (introduced in
> v1.5.x - http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-hooks).
> Though it probably means a bit of work for you to do.

Thanks; I'm taking a look at it.

I wonder if it would really be possible using those; because I would
either need to encrypt the files in-place in the pre-commit hook (bad,
obviously, as they'd probably currently be open in an editor) or I'll
need to reject the entire commit and commit my own encrypted copies
that I've generated somewhere else on disk.

Post-update would have the same problems in that I'd get the encrypted
version down and 'saved' to it's location, then I'd need to go and
decrypt it in-place. Not ideal.

I don't mind doing the work myself if there is a way (infact, I'd
build the decryption into other programs that hook into svn anyway
[like cruise control, and my own deployment tool]) but I just don't
think the local script hooks are enough ...

> --
> Milen A. Radev

-- 
noon silky
http://skillsforvilla.tumblr.com/
http://www.themonkeynet.com/armada/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org