Forbid uncommits over the network

[Lasse Kliemann]

* Message by -John Arbash Meinel- from Fri 2009-05-08:

> So it would appear that I was wrong. I just checked the code, and
> 'append_revisions_only' supersedes '--overwrite'.
> 
> append_revisions_only is actually checked at the time of
> 'set_last_revision_info', which is just about as low-level as you can get.

This sounds good so far. However...

> So with the existing bzr clients, you can't override that setting.
> (There are ways someone with write access to that file could write a
> specific value there, but it would have to be pretty much malicious, and
> not accidental in any way.)

Well, I am considering the case of a malicious person gaining 
access to the credentials of a committer.

Do I understand correctly that we have a kind of client-side 
"security" here, i.e., a setting that should protect the server 
and is set on the server (namely 'append_revisions_only') can be 
overwritten by an appropriately programmed client?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090508/ed558893/attachment.pgp