[bug-notifications] [openssh 0004367]: Sshd version OpenSSH_5.4p1 refuses to start on SPARC Solaris 10 zone

Mantis Bug Tracker noreply at opencsw.org
Tue Mar 23 11:09:28 CET 2010


A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/bugtrack/view.php?id=4367 
====================================================================== 
Reported By:                matti123
Assigned To:                
====================================================================== 
Project:                    openssh
Issue ID:                   4367
Category:                   regular use
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2010-03-23 10:09 CET
Last Modified:              2010-03-23 11:09 CET
====================================================================== 
Summary:                    Sshd version OpenSSH_5.4p1 refuses to start on SPARC
Solaris 10 zone
Description: 
Today I installed lots of packages from current repository to a new Solaris
10 zone. One of the packages was CSWossh. Version OpenSSH_5.4p1, OpenSSL
0.9.8m 25 Feb 2010 outputs error message "derelativise_path: getcwd:
Invalid argument" and refuses to start.

Previous version, OpenSSH_5.3p1, OpenSSL 0.9.8l 5 Nov 2009, which I
installed about a week ago runs without any problems.
====================================================================== 

---------------------------------------------------------------------- 
 (0007728) matti123 (reporter) - 2010-03-23 11:09
 http://www.opencsw.org/bugtrack/view.php?id=4367#c7728 
---------------------------------------------------------------------- 
I was able to track the cause to this issue. After uncommenting a following
line from sshd_config sshd refuses to start.

#AuthorizedKeysFile     .ssh/authorized_keys

So the line should be left in comments. This is a little bit strange thing
because above value should be default even if it's commented.



More information about the bug-notifications mailing list