Config file semantics change intentional?

[mouring at etoh.eviladmin.org]

This has been resolved in the latest CVS tree and will be fixed in 3.0

On Wed, 24 Oct 2001, Dan Astoorian wrote:

> In 2.3.0, the per-user config file was read before the system-wide
> config file, so options set in ~/.ssh/config took precedence over
> system-wide defaults.  In 2.9.9, the system-wide file seems to be read
> first, contrary to the man page (cf. ssh.c ll. 631-632).
>
> It seems to me that the old behaviour made more sense.  (I discovered
> the change because I could not override a "ForwardX11" option for a
> particular host when it was specified in the global client config file
> for all hosts.)
>
> Is this a deliberate change, and the man page hasn't been updated?  Or
> should ssh.c be corrected to read the system-wide config file after the
> per-user config file?
>
> --
> Dan Astoorian               People shouldn't think that it's better to have
> Sysadmin, CSLab             loved and lost than never loved at all.  It's
> djast at cs.toronto.edu        not, it's better to have loved and won.  All
> www.cs.toronto.edu/~djast/  the other options really suck.    --Dan Redican
>