Bug 930 - two configure warnings
Summary: two configure warnings
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Build system (show other bugs)
Version: 3.8p1
Hardware: SPARC Solaris
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-17 01:05 AEST by Christopher L. Barnard
Modified: 2006-10-07 11:37 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher L. Barnard 2004-09-17 01:05:09 AEST
I do not know if these are critical or not, but I want to pass them along.

I am on a Sun blade 150 running Solaris 9 with just about all packages installed
and current with patches.  This is with the ./configure for OpenSsh version
3.9p1.  I run ./configure with the options --with-tcp-wrappers
--with-pid-dir=/var/run --with-mantype=cat --sysconfdir=/etc
--with-ssl-dir=/usr/local/ssl.  (ssl is OpenSSL 0.9.7d).  configure has the
warning in the middle 

configure: WARNING: sys/ptms.h: present but cannot be compiled
configure: WARNING: sys/ptms.h:     check for missing prerequisite headers?
configure: WARNING: sys/ptms.h: see the Autoconf documentation
configure: WARNING: sys/ptms.h:     section "Present But Cannot Be Compiled"
configure: WARNING: sys/ptms.h: proceeding with the preprocessor's result
configure: WARNING: sys/ptms.h: in the future, the compiler will take
precedenceconfigure: WARNING:     ## ------------------------------------------ ##
configure: WARNING:     ## Report this to the AC_PACKAGE_NAME lists.  ##
configure: WARNING:     ## ------------------------------------------ ##

final summary of the configuration says
WARNING: the operating system that you are using does not 
appear to support either the getpeereid() API nor the 
SO_PEERCRED getsockopt() option. These facilities are used to 
enforce security checks to prevent unauthorised connections to 
ssh-agent. Their absence increases the risk that a malicious 
user can connect to your agent.
Comment 1 Darren Tucker 2004-10-06 20:47:37 AEST
Thanks, they're both warnings.  The first has already been fixed (after the
3.9p1 release).

The second is a warning about the platform's lack of any way to determine the
effective uid of the process connecting to ssh-agent's socket.  This has always
been the case, but the warning is new.  (If anyone knows a way implement
getpeereid() on Solaris, please let us know).
Comment 2 Darren Tucker 2006-10-07 11:37:08 AEST
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.