Bug 23753 - xinetd fails to set REMOTE_HOST environment
xinetd fails to set REMOTE_HOST environment
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: xinetd (Show other bugs)
7.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-10 17:50 EST by jwitford
Modified: 2007-04-18 12:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-06 18:16:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
xinetd patch for REMOTE_HOST environment variable (2.71 KB, patch)
2001-01-10 17:51 EST, jwitford
no flags Details | Diff
xinetd patch for REMOTE_HOST environment variable (2.68 KB, patch)
2001-01-10 18:58 EST, jwitford
no flags Details | Diff

  None (edit)
Description jwitford 2001-01-10 17:50:00 EST
xinetd fails to correctly set the REMOTE_HOST environment variable.

Although there is a setenv("REMOTE_HOST",..) the code has
presumeably been upgraded to support the "env" and
and "passenv" configuration settings.
Consequently xinetd's environment is not the appropriate
place to add the REMOTE_HOST environment variable.
Comment 1 jwitford 2001-01-10 17:51:56 EST
Created attachment 7404 [details]
xinetd patch for REMOTE_HOST environment variable
Comment 2 jwitford 2001-01-10 18:58:11 EST
Created attachment 7405 [details]
xinetd patch for REMOTE_HOST environment variable
Comment 3 jwitford 2001-01-10 19:04:51 EST
My earlier patch was faulty because of unforseen changes in pre11 which
affected the connection client address.

Unfortunately the latest changes in connection.c also deny client
programs access to REMOTE_HOST if xinetd waits.

Comment 4 Trond Eivind Glomsrxd 2001-01-11 14:21:22 EST
In which cases would that be a problem?
Comment 5 jwitford 2001-01-11 16:34:31 EST
Any servers that have "wait = yes" and which need to know the
client IP address need to have REMOTE_HOST set in their environment.
For instance, a shell script, because it cannot do the equivalent of
getpeername() on file descriptor 0.


Comment 6 Trond Eivind Glomsrxd 2001-01-15 12:53:21 EST
Do you have a specific example I can use for testing, verifying fix etc?
Comment 7 jwitford 2001-01-16 03:36:56 EST
After considerable thought and effort I have been able to
create an innocuous example for you.

#! /bin/sh
traceroute -n $REMOTE_HOST >>log 2>&1



Comment 8 Trond Eivind Glomsrxd 2001-02-06 18:02:39 EST
Could you try the xinetd-2.1.8.9pre14-5 RPMS you can find at
http://people.redhat.com/teg/ and see if they solve the problem?
Comment 9 Trond Eivind Glomsrxd 2001-02-12 20:16:04 EST
This works with xinetd-2.1.8.9pre14-5, possibly earlier ones as well.

Note You need to log in before you can comment on or make changes to this bug.