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

question about encryption

From: <svn-dev_at_cxxl.de>
Date: 2005-09-19 10:26:37 CEST

hi,

i hope this is the right place to ask for this:

i'm looking for a solution to this problem: i use SVN for one year now
and am very happy with it. until now, i use it only for myself. now,
i'd like a second user to access the repo as well. since i don't
operate my machine 24/7, we'd need to use some server. but we don't
want to have to trust the server's operators not to copy the repo for
whatever reasons for themselves.

what could be the solution? sure, i could run my box 24/7, but this
brings up other issues (like me not being a good admin, intrusions,
etc..). i was asking myself if SVN couldn't do what i need...

could one add to SVN the ability to manage an encrypted repo and only
decrypt it on the client side? in case anybody stole the repo or
listened to the communications, he wouldn't get anything legible. the
client(s) would know how to decrypt the data and how to interpret it.

somehow i think it should not be too hard to implement this. assuming
you were using some cipher algorithm in ECB mode, you only needed to
replace all calls of write(h, buf, cnt) with write(h, encrypt(buf),
cnt) and vice versa with read() (i know, i'm simplifying, i just want
to make a point).

what do you think of this?

ps: maybe this is some strange idea. if so, i'd like to know how
other people solved similar problems. with so many people working
from home, there must be someone with alike settings.

-- 
/chris/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 19 10:27:08 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.