On Tue, Jun 22, 2010 at 04:41:45PM -0400, Chris Ball wrote: > > You could, perhaps, disable that particular command with some > > be-serve hackery... > > I think that's a good idea (behind a config option), and other users > of be serve might benefit from it too.
I agree about it not being a good idea. A note to anyone interested in more granularity than read/write: `be serve` acts on the (Versioned)Storage interface, so its hard to implement per-command permissions. You can, however, easily put in permissions at the Storage-level, and "commit" has the luck of existing distinctly at both levels. All you'd need is some sort of sane configuration procedure... ;) -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpH3MfeTRB03.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
