On 10/06, Martin Ågren wrote: > On 6 October 2017 at 11:40, Junio C Hamano <gits...@pobox.com> wrote: > > Simon Ruderich <si...@ruderich.org> writes: > > > >> Did you consider Stefan Beller's suggestion regarding a > >> (white)list of allowed versions? > >> > >> On Mon, Sep 18, 2017 at 01:06:59PM -0700, Stefan Beller wrote: > >>> Thinking about this, how about: > >>> > >>> If not configured, we do as we want. (i.e. Git has full control over > >>> it's decision making process, which for now is "favor v0 over v1 as > >>> we are experimenting with v1". This strategy may change in the future > >>> to "prefer highest version number that both client and server can > >>> speak".) > >>> > >>> If it is configured, "use highest configured number from the given set". > >>> > >>> ? > >> > >> It would also allow the server operator to configure only a > >> specific set of versions (to handle the "version x is > >> insecure/slow"-issue raised by Stefan Beller). The current code > >> always uses the latest protocol supported by the git binary. > > > > If we do anything less trivial than "highest supported by both" (and > > I suspect we want to in the final production version), I'd prefer > > the configuration to list versions one side supports in decreasing > > order of preference (e.g. "v3 v0 v2"), and take the earliest from > > this list that both sides know how to talk, so that we can skip > > insecure versions altogether by omitting, and we can express that we > > would rather avoid talking expensive versions unless there is no > > other version that is understood by the other side. > > Maybe I'm missing something Git-specific, but isn't the only thing that > needs to be done now, to document/specify that 1) the client should send > its list ordered by preference, 2) how preference is signalled, and 3) > that the server gets to choose? > > Why would a server operator with only v0 and v1 at their disposal want > to choose v0 instead of v1, considering that -- as far as I understand > -- they are in fact the same? > > Different server implementations and different server configurations > will be able to apply whatever rules they want in order to decide which > version to use. (It's not like the client can verify the choice that the > server makes.) And Brandon's "pick the highest number" will do for now. > > There are many possible rules that the server could apply and they > shouldn't affect other servers or what the client does. For example, the > server can go "You seem to know lots of versions, including X and Y. > Those are the two that I really prefer, but between those two I'm not > picky, so I'll use whichever of X and Y that you seem to prefer." Unless > I've missed something, we'll never need to implement -- nor specify -- > anything like that before we have learned both v2 and v3. > > I guess my thinking is, there's a difference between the protocol and > the implementation.
I've been busy the last week or so and I probably wont get much more time to go into more detail on this until the end of the week, so sorry for not being super active on this thread in the past couple of days. One of the key things about this transition is ensuring that we get it right, because if we get it wrong and find out years later we'll have to live with it. So I'm excited and happy that people are taking a close look at this. That being said I don't think we need to worry too much about how one version of the protocol is selected over another. I fully expect this to change based on many different factors. Maybe one particular server implementation favors v4 over v5, or another serve has no preference at all. We may learn something later on, based on security or other reasons, that we want to prefer one version or another. Because of that (and because I'm hoping that once we have a v2 built that we don't have to move to another protocol version any time soon) I think it would be a mistake to hard-code or design in inherent preferences that a client expresses that servers are 'required' to respect. So I agree with Martin here that if more complicated use cases arise we can design in a preference system for them at a later time. Given some of this discussion though, maybe we want to change the semantics of 'protocol.version' so that both servers and clients respect it. As of right now, these patches have the server always allow protocol v0 and v1? Though that doesn't do much right now since v1 is the same as v0. One other considerations that I should probably handle is that a client doesn't do any verification right now to ensure that the protocol version the server selects was indeed the protocol that the client requested. Is that something you think we need to check for? -- Brandon Williams
