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

Re: Encrypted Repositories. . .?

From: Benjamin Podszun <ben_at_galactic-tales.de>
Date: 2007-06-21 01:06:54 CEST

Michael Williams schrieb:
> You're allowed an opinion, but frankly I'm not concerned what you
> think. My only concern is what's possible. I honestly don't believe
> it's that huge of a problem. And again, as I've said: Just because
> it's not being done, doesn't mean it can't or shouldn't be. I believe
> on-disk encryption is a great and useful idea to have incorporated
> into SVN.
Disclaimer: No offense intended. This is a discussion about the proposed
feature alone, so don't take anything personal please.

Allow me an opinion as well: You don't believe it's that huge of a
problem, but still everyone but you comes up with problems that you
might not have thought about or ignore right away - which basically
makes the discussion about security a moot point again.
Same applies to the encryption for SVN. No one agreed so far and I
really don't want this to sound personal, but you might just want
something that is useful for only one: You. If even at all, but that's
not the point, currently.
Following the "One tool for the job" philosophy I'm happy with svn as it
is now. It does what it should do: Keeping your revision history. There
are solutions for encryption, but they have nothing to do with svn and
that's a good thing in my book.
Do you know one other "competing" product that delivers what you want?
If not (because I don't): Maybe there's no market for that. Okay, I have
to admit that I have little understanding for the "Protect the sources
at all cost" stuff anyway, since I'm privately using open-source and my
company delivers the source with the product, but I do understand that
you want to protect it for whatever reasons, and protect it in a
different way than everyone suggested.
I see only one route to follow here: Either you really want this
feature. In that case you could easily go for a branch/fork/patchset and
try to build it yourself (The chance that some other guy built it before
is probably pretty low, looking at the responses so far). Or you have to
rely on the methods given here, maybe with some extra paranoia (again,
no offense) at the system administration level.

I frankly believe that your solutions/proposals so far are broken by
design and don't work, but if they do what you want or let you sleep
better at night: Why don't you just go for it?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 21 01:07:31 2007

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

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