On Thu, Apr 17, 2008 at 10:44 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Having said that, the current "clone" implementation may happen to ignore > in-tree anything, <snip> > But I consider that is not by design, but is a limitation of the current > implementation that can be improved. I think it -should- be by design that it ignores everything unless we are certain that it is safe to do so. So as long as an in-tree doesn't provide any hooks to execute things (which of course includes changing the environment) it should be fine, but if it is, it should be ignored till after clone has finished. Because of that an in-tree '.gitconfig' would have no security risks as long as it is not 'used' until after the clone. This would be easy to make sure of by not syncing it with the real '.gitconfig' until after cloning. (That is assuming there will be some sort of syncing to the real 'gitconfig' from the in-tree '.gitconfig', if a fall-back type of mechanism is chosen that might be more difficult) Cheers, Sverre Rabbelier -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
