On 02/05/2013 09:33 AM, Jonathan Nieder wrote: > Michael Haggerty wrote: > >> I would again like to express my discomfort about this feature, which is >> already listed as "will merge to next". Frankly, I have the feeling >> that this feature is being steamrolled in before a community consensus >> has been reached and indeed before many valid points raised by other >> members of the community have even been addressed. For example: > > In $dayjob I work with Gerrit, so I think I can start to answer some > of these questions. > >> * I didn't see a response to Peff's convincing arguments that this >> should be a client-side feature rather than a server-side feature . > > The client can't control the size of the ref advertisement. That is > the main motivation if I understood correctly.
Not according to Junio : Look at this as a mechanism for the repository owner to control the clutter in what is shown to the intended audience of what s/he publishes in the repository. Network bandwidth reduction of advertisement is a side effect of clutter reduction, and not necessarily the primary goal. >> * I didn't see an answer to Duy's question  about what is different >> between the proposed feature and gitnamespaces. > > Namespaces are more complicated and don't sit well in existing setups > involving git repositories whose refs are not namespaced. Thanks. >> * I didn't see a response to my worries that this feature could be >> abused . > > Can you elaborate? Do you mean that through social engineering an > attacker would convince the server admin to store secrets using a > hidden ref and enable the upload-archive service? The upload-archive service is not needed; after patch v3 "7/8" remote clients are able to retrieve hidden content by SHA1. Hiderefs creates a "dark" corner of a remote git repo that can hold arbitrary content that is impossible for anybody to discover but nevertheless possible for anybody to download (if they know the name of a hidden reference). In earlier versions of the patch series I believe that it was possible to push to a hidden reference hierarchy, which made it possible to upload dark content. The new version appears (from the code) to prohibit adding references in a hidden hierarchy, which would close the main loophole that I was worried about. But the documentation and the unit tests only explicitly say that updates and deletes are prohibited; nothing is said about adding references (unless "update" is understood to include "add"). I think the true behavior should be clarified and tested. I was worried that somehow this "dark" content could be used for malicious purposes; for example, pushing compromised code then convincing somebody to download it by SHA1 with the implicit argument "it's safe since it comes directly from the project's official repository". If it is indeed impossible to populate the dark namespace remotely then I can't think of a way to exploit it. > That does sound like a reasonable concern. Perhaps the documentation > should be updated along these lines > > transfer.hiderefs:: > String(s) `upload-pack` and `receive-pack` use to decide > which refs to omit from their initial advertisement. Use > more than one transfer.hiderefs configuration variables to > specify multiple prefix strings. A ref that are under the > hierarchies listed on the value of this variable is excluded, > and is hidden from `git ls-remote`, `git fetch`, `git push :`, > etc. An attempt to update or delete a hidden ref by `git push` > is rejected, and an attempt to fetch a hidden ref by `git fetch` > will fail. > + > This setting does not currently affect the `upload-archive` service. > > until someone interested implements the same for upload-archive. Yes, this sounds reasonable. >> I also think that the feature is poorly designed. For example: > > That's another reasonable concern. It's very hard to get a design > correct right away, which is presumably part of the motivation of > getting this into the hands of interested users who can give feedback > on it. What would potentially be worth blocking even that is concerns > about the wire protocol, since it is hard to take back mistakes there. > >> * Why should a repository have exactly one setting for what refs should >> be hidden? Wouldn't it make more sense to allow multiple "views" to be >> defined?: > > How do I request a different view of the repository at > /path/to/repo.git over the network? How can we make the common case > of only one view easy to achieve? Isn't the multiple-views case > exactly what gitnamespaces is for? Hidden references can only be configured by somebody with local access to the repository being served. Somebody with that access could also configure views. He could also probably organize a mapping from URL -> (GIT_PATH, GIT_VIEW) and offer several different views of the same repository. If the setting of environment variables is thought to sometimes be too problematic, the default view could be defined via configuration, too: [view] default = official [view "official"] hiderefs = refs/pull Or perhaps, if views are made available locally too, then one view could be designated as the default for transfer purposes: [transfer] defaultview = official gitnamespaces have the disadvantage that you mentioned yourself earlier. > [...] >> * Is it enough to support only reference exclusion (as opposed to >> exclusion and inclusion rules)? > > The motivating example is turning off advertisement of the > refs/changes hierarchy. If and when more complicated cases come up, > that would presumably be the time to support more complicated > configuration. I suppose should the need arise we could later introduce "transfer.showrefs" and let the longest match to a given reference (i.e., "transfer.hiderefs" vs. "transfer.showrefs") win. > [...] >> * Why should this feature only be available remotely? > > It is about transport. Ref namespaces have their own set of use cases > and are a distinct feature. gitnamespaces offer multiple perspectives of a single object database, using independent sets of references to define the subset. Changing a reference in one namespace has no effect on similarly-named references in another namespace. The "views" feature that I vaguely suggested, on the other hand, would offer multiple subsets of a single set of references, a bit like an SQL view. Changing a reference in one view would automatically affect it in other views that include the reference. It could be a handy way to reduce clutter *locally* in the same way that hiderefs would reduce clutter *remotely*. But more importantly, both features could be built on the same foundation. Michael  http://article.gmane.org/gmane.comp.version-control.git/213984 -- Michael Haggerty mhag...@alum.mit.edu http://softwareswirl.blogspot.com/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html