Bug 185277

Summary:	Security: Portmap interface control and sysconfig file
Product:	[Fedora] Fedora	Reporter:	Kevin Verma <kevinverma>
Component:	portmap	Assignee:	Steve Dickson <steved>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	https://launchpad.net/distros/ubuntu/+source/portmap/+bug/7265
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-07-11 13:24:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin Verma 2006-03-13 06:51:31 UTC

Description of problem:
Suggesting an enhancement to existing portmap

Version-Release number of selected component (if applicable):
all

How reproducible:
Portmap either listens to all interfaces or only on loopback,

Expected results:
This should also let have a control feature with option -i to optionally bind
portmap to particular network interface. Also an /etc/sysconfig/portmap is
wished for. 

Additional info:
https://launchpad.net/distros/ubuntu/+source/portmap/+bug/7265

Comment 1 Steve Dickson 2007-07-11 13:24:23 UTC

ther is a -l that "causes portmap to only bind to the loopback 
interface (i.e. INADDR_LOOPBACK)." as well as a 
[ -f /etc/sysconfig/$prog ] && . /etc/sysconfig/$prog in 
the /etc/init.d/portmap start up script.