On Wed, 10 Apr 2002, Gerhard Sittig wrote:
On Wed, Apr 10, 2002 at 18:08 +0200, Roland Kuhn wrote:
On Wed, 10 Apr 2002, Joerg Ruhe wrote:
My trouble is, I'm observing a differnt behaviour ( as you can see in the log below ): OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Reading configuration data /home/ruhej/.ssh/config debug1: Applying options for *
Here the options in the system-wide configuration file are applied first. I have seen this on several differnt computers, all with SuSE 7.3 and openssh 2.9.9p2 .
From an algorithmic standpoint it would make sense to read the configuration files in reverse order, but this doesn't mean anything. Did you experience a setting in /etc/ssh/ssh_config overriding a user setting?
No, I would always implement option scanning in the way it's done above (start with defaults and override them should there be parameters with higher precedence). Otherwise you had to do some bookkeeping about which options you have seen and thus did set -- only to not apply another parameter with lower precedence. This would mean more effort prone to errors (put a flag next to _every_ setting if it has been specified in a previously read config) for no gain (you still have to read all the configs and get the same resulting set of options).
Sure, this is what I meant (from an algorithmic standpoint...). However, the ssh man page states that options set at the beginning of each file take precedence over options specified later. Either the file is read backwards or this book keeping is done. Ciao, Roland +---------------------------+-------------------------+ | TU Muenchen | | | Physik-Department E18 | Raum 3558 | | James-Franck-Str. | Telefon 089/289-12592 | | 85747 Garching | | +---------------------------+-------------------------+