Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: William Unruh <unruh@invalid.ca>
Newsgroups: alt.os.linux.mageia,comp.os.linux.security
Subject: portmap/rpcbind and tcpwrapper
Followup-To: alt.os.linux.mageia,comp.os.linux.security
Date: Thu, 1 Oct 2015 07:48:18 +0000 (UTC)
Organization: A noiseless patient Spider
Lines: 10
Message-ID: <muiog2$qbj$1@dont-email.me>
Injection-Date: Thu, 1 Oct 2015 07:48:18 +0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="bce60fb4c4f81b126f867f22d396ac27"; logging-data="26995"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19pPMLoNE39qQ9HTeZ6AEKd"
User-Agent: slrn/1.0.1 (Linux)
Cancel-Lock: sha1:l3P8ZBvLtcg34TCUsgU0VfNoew0=
Xref: csiph.com alt.os.linux.mageia:10700 comp.os.linux.security:660

portmap/rpcbind is supposed to controllabl by tcpwrapper. I have a line
rpcbind portmap: ALL:deny

in /etc/hosts.allow after a line
rpcbind portmap: 192.168.0.0/24 : allow

But then I can still run rpcinfo on a machine from outside that network
and et responses.
Does rpcbind respect tcpwrapper or not?