FS#7096 - Portmap doesn't use tcpwrapper
Attached to Project:
Arch Linux
Opened by Olivier Médoc (oliv) - Tuesday, 08 May 2007, 10:13 GMT
Last edited by Allan McRae (Allan) - Thursday, 25 December 2008, 06:04 GMT
Opened by Olivier Médoc (oliv) - Tuesday, 08 May 2007, 10:13 GMT
Last edited by Allan McRae (Allan) - Thursday, 25 December 2008, 06:04 GMT
|
Details
I found today that portmap isn't linked with libwrap, and
access isn't ruled by /etc/hosts.deny
I don't know if it's a bug but most of servers are using libwrap in arch linux (ssh, ldap, ...). |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 25 December 2008, 06:04 GMT
Reason for closing: Fixed
Additional comments about closing: Also, no response from submitter to status query.
Thursday, 25 December 2008, 06:04 GMT
Reason for closing: Fixed
Additional comments about closing: Also, no response from submitter to status query.
WRAP_LIB=/usr/lib/libwrap.a make || return 1
Than ldd results the same as i can see on my server with opensuse and i suggest this or another way to get portmap linked dynamically against tcp-wrapper library
(By the way, aren't those .a files from libtool? We don't (or try) not to use those anymore?)
$ ldd $(which portmap)
linux-vdso.so.1 => (0x00007fff9a1fe000)
==> libwrap.so.0 => /usr/lib/libwrap.so.0 (0x00007f1391d20000) <==
libc.so.6 => /lib/libc.so.6 (0x00007f13919cc000)
libnsl.so.1 => /lib/libnsl.so.1 (0x00007f13917b4000)
/lib/ld-linux-x86-64.so.2 (0x00007f1391f28000)
$ pacman -Q portmap
portmap 6.0-2
Olivier - if you're still around, and you still have this problem, let me know. Otherwise, it's a non-bug.
I would still like to hear from the OP about how he found the bug, but as it's 18 months since he reported it, and he hasn't responded to my previous request, I'm beginning to think he's moved on.