[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

feature request: encrypt before commit, decrypt after update

From: silky <michaelslists_at_gmail.com>
Date: Tue, 14 Oct 2008 09:41:31 +1000

Hello,

 I hope this is the appropriate forum to request a feature.

 I'm looking for the ability to add a *client-side*
encryption/decryption process to the commit/update process of SVN. It
would work like so:

 * Person 1 creates new project *
 1. Work on local, unecrypted, files as per normal
 2. Create "encrypted" repo by assigning an AES private key to the repo
 3. Commit the work
   3a. All files are encrypted client-side and then sent up
 4. Commit finishes

 --

 * Person 2 wants to get the 'encrypted' repo *
 1. Creates local area, assigns it the AES private key given to him by person 1
 2. Gets latest version
 3. Comes down as per normal; files decrypted client-side
 4. Able to work and commit as per previous

 I realise this would probably break a few things; I'd be interested
to hear what they were and the general chances of this being included.
I really like it because it would allow me to host sensitive projects
(and files) on public servers (assembla, paid ones, etc). Should also
be fairly trivial to do.

 Let me know if I haven't been clear. Note that this is obviously
different from SSL/SSH which obviously already exists.

-- 
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
Received on 2008-10-14 01:41:45 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.