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

Re: Making file immutable in working copy

From: Lasse Kliemann <lasse-subversion-users-2004_at_plastictree.net>
Date: Sun, 28 Sep 2008 15:04:28 +0200

* Message by -David Weintraub- from Sat 2008-09-27:
> So, you want to prevent someone, on a system they control, not to be
> able to modify files?

No. I want to give users the _option_ of marking certain files in
their working copy as immutable to 'svn up' operations.

> By the way, how do you mean that the repository was compromised?

Someone breaks into the server, by whatever means. Then the
attacker replaces the repository by a specially crafted one. This
new repository looks like the old one to the 'svn' client, so the
'svn up' operations run smoothly. However, the new repository
does not contain certain important files - in no revision. So,
users do 'svn up', and the important files get deleted in their
working copies. Any attempts to get these files from previous
revision fail, since also the previous revisions (if any at all;
that depends on how the new repository was crafted in detail) do
not contain these files.

  • application/pgp-signature attachment: stored
Received on 2008-09-28 14:36:18 CEST

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.