Bug 786

Summary:	ssh is still looking at default config file when it is about EnableSSHKeysign
Product:	Portable OpenSSH	Reporter:	Marius I.Giuglea <blueseawolf>
Component:	ssh	Assignee:	OpenSSH Bugzilla mailing list <openssh-bugs>
Status:	CLOSED WONTFIX
Severity:	normal
Priority:	P2
Version:	3.7p1
Hardware:	ix86
OS:	Linux

Description Marius I.Giuglea 2004-01-10 11:15:08 AEDT

ssh protocol 2 / hostbased authentication 
 
As you know in order for ssh to work with hostbased authentication 
the flag EnableSSHKeysign must be set to "yes" in ssh_config file 
 
That worked. 
 
But if an alternate config file is specified in ssh command line as: 
 
# /openssh/bin/ssh -F /openssh/etc/ssh_config_2 -v [hostname]  
 
does not work 
 
also this flag (EnableSSHKeysign) is not taken as an -o argument in command line: 
 
# /openssh/bin/ssh -F /openssh/etc/ssh_config_2 -o EnableSSHKeysign=yes -v [hostname] 
 
does not work 
 
I belive ssh is looking at the default config file when it is about this particular flag since there is 
a message when using -v option with ssh saing: 
 
"ssh-keysign not enabled in /openssh/etc/ssh_config"  ...and this is the default config file 
 
As I said I used -F /openssh/etc/ssh_config_2 and I'm absolutely sure this alternate file is 
used since other options such as port number are corectly taken from alternate config file. This 
is all about EnableSSHKeysign flag only. 
 
We need this in a Linux based diskless cluster

Comment 1 Markus Friedl 2004-01-10 11:29:18 AEDT

EnableSSHKeysign is not a flag used by the ssh client,
so -o or -F do not matter.

only the sysadmin can set this flag in /etc/ssh/ssh_config.

Comment 2 Damien Miller 2004-02-10 13:44:52 AEDT

This behaviour is by-design

Comment 3 Damien Miller 2004-04-14 12:24:20 AEST

Mass change of RESOLVED bugs to CLOSED