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

Re: Limiting access to replay in 1.4

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2006-04-08 05:59:45 CEST

On 4/7/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> And I also worry about that. I'm kind of curious how noticable things
> would be tough. I mean it wouldn't actually be EVERY read request,
> just the significant reports really, but still. I think it's worth
> prototyping and benchmarking though, just to see if it's actually
> noticable.

Sure, but I'm thinking of the implications of a hook script on the
update report more than I am about the replay report. You'd have to
execute the hook on every path in the update report to see whether it
is allowed or not (passing all paths on the command-line would
overwhelm some OS limits on number of arguments). It's essentially
another form of authz with the same 'check every path' semantics. --
justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 8 06:00:14 2006

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.