similar to: libwrap does it work on in 2.0?

I'm trying to kickstart 2.0b3 on my NetBSD system (where 1.2.x works great!), and keep hitting: Fatal: service(tcpwrap) access(/software/dovecot-2.0beta3/libexec/dovecot/tcpwrap) failed: No such file or directory Indeed, that file doesn't exist...but I don't have nor want libwrap. It appears that doveconf includes tcpwrap... service tcpwrap { chroot = client_limit = 1

All, There was some discussion recently on Ubuntu Launchpad regarding the bug in NUT 2.2.1 where it was not possible to connect with an accept- all ACL: https://bugs.launchpad.net/bugs/235653 The package was patched for the upcoming Ubuntu release (intrepid), but the discussion drifted to the merits of application-level ACLs (comment 11 and beyond). Steve Langasek brings up a good point

Hi all. Now that we have SSHDLIBS for the libraries required by sshd only, it's possible to remove some of the single-purpose variables from Makefile. If this is worth doing, the next step would probably be to move the OpenSSL libs into CRYPTOLIBS since binaries such as scp and sftp don't need to be linked with libcrypto. Index: Makefile.in

Hello, There is a small but annoying problem with linking libwrap in openssh. The library is added to LIBS which makes it be linked in to all binaries. This is unnecessary and leads to bogus dependencies if libwrap is a shared library. Following is a trivial fix that reserves a separate autoconf substitution variable LIBWRAP, which is only used for sshd. Please apply. Maciej -- +

Hi all, I've hit a problem with OpenSSH 2.1.1p4 and TCP Wrappers, and have noticed others may also have seen the problem. When OpenSSH is compiled with wrapper support, access using standard userid/password fails - authentication works ok and a shell is gained and then immediately terminated. Running client in debug mode shows no obvious errors, and debug output from syslog also reveals

Hello all, I have been having some trouble getting my Icecast server and IceS streamer up and running properly. I have successfully compiled both (Icecast 1.3.10 and IceS 0.0.1beta5) with libwrap and encrypt enabled. I can start up Icecast fine, with the following logged messages on startup: Icecast Version 1.3.10 Initializing... Icecast comes with NO WARRANTY, to the extent permitted by law.

On Wed, 20 May 2015 14:46:57 +0200 Peter Stuge <peter at stuge.se> wrote: > Stephan von Krawczynski wrote: > > it is pretty obvious > > I guess you're not only not subscribed to the development list, but > you seem to also not have looked at the list archives. > > You can only seem like a troll if you act as if you know best but > in fact you are wrong.

Since I've been using this for maybe a year now, maybe someone else is interested in restricting IMAP and POP logins via libwrap. In addition to the attached patch (against 1.0.5) to src/login-common/main.c, src/{imap,pop3}-login/Makefile.in have to be modified to link against libwrap. Of course, the option needs to be integrated into configure in the long run. -------------- next part

On Tue, 17 Apr 2001, Andrew M. Wu wrote: > Hello all, > > I have been having some trouble getting my Icecast server and IceS > streamer up and running properly. I have successfully compiled both > (Icecast 1.3.10 and IceS 0.0.1beta5) with libwrap and encrypt enabled. > > I can start up Icecast fine, with the following logged messages on > startup: > > Icecast

Hello there, I have been trying to make the patch work for libwrap(TCP Wrappers) posted on http://dovecot.org/patches <http://dovecot.org/patches%20Patch%20of%201.1> Patch of 1.1 but could not get it work. Any help will be highly appreciated. After compiling and running it I get error "Error: login_tcp_wrappers can't be used because Dovecot wasn't built with

Hi! Here is the patch to support tcp wrappers with x11-forwarded connections. The patch is for openssh-3.0.1p1 but it works fine with 2.9.9p2 too. I've understood that this will not be included in the official version because it adds complexity (?!) to openssh. Binding the forwarded port to localhost doesn't solve all problems. I've understood that you should also implement

Hello all, after a useless discussion on the opensuse ML I had to find out that they buried the removal news of libwrap last year in some half-sentence. So this is unfortunately pretty late for the topic. Nevertheless it is pretty obvious that you did not get any feedback from people using ssh over decades in server-administration. Let me make a clear point: libwrap removal was a pretty bad idea.

Hi, A few things regarding logging and libwrap.. a) PAM_RHOST patch Back in July, dean gaudet helpfully posted a patch to dovecot PAM_RHOST the remote IP. Is this going to be included in the main dovecot tree? It seems like a worthwhile addition. The more informative and concise the logging the better. See http://www.dovecot.org/list/dovecot/2004-July/004011.html for the original message.

On Fri, 25 Nov 2016, Jonah Naylor wrote: > I don't think nut is built with TCP wrappers support, although the > package is listed as depending on libwrap... Why would you have such a dependency if nut didn't use TCP Wrappers? > I ran this command: ldd /sbin/upsd | grep libwrap.so and it has returned > no output. If I run that command I get maria:~ # ldd /usr/sbin/upsd

I finally started looking into how to use libwrap, and even got the code working: http://dovecot.org/patches/1.0/tcp-wrappers.patch However once everything was done, I realized it can't work that way because login processes are normally chrooted. So if you want TCP wrappers and don't care that much about the security given by chrooting, you could disable it and use the above patch.

Hi thanks for helping. I don't think nut is built with TCP wrappers support, although the package is listed as depending on libwrap... I ran this command: ldd /sbin/upsd | grep libwrap.so and it has returned no output. Does this mean I have to compile from source or is there a way to add the tcp wrapper support? Thanks again. On 24 November 2016 at 22:40, Roger Price <roger at

Feb 12 CVS (sort of, see warning below) I've had to change around some of the code in configure.in to get some platforms to compile with the --with-tcp-wrappers option. Basicly I have set it up to check headers check system libraries check for optional packages check functions I have also tried to clean up the library order as it is important on some platforms. This patch works on Solaris

On Thu, May 21, 2015 at 1:05 AM, Michael Stone <mstone at mathom.us> wrote: > On Wed, May 20, 2015 at 03:58:22PM +0200, Stephan von Krawczynski wrote: > >> Show me this as an example of your firewall skills and replace this >> hosts.allow entry: >> >> sshd: .... : spawn (echo -e "%u@%h[%a] on `/bin/date`" to %d connected >> me | >>

Hi thanks Roger. Well I'm just using Ubuntu Server 16.04 LTS I only ran that command as a few guides say that's how to establish if a daemon is compiled with tcp wrappers: https://www.cyberciti.biz/faq/tcp-wrappers-hosts-allow-deny-tutorial/ I haven't really used TCP wrappers before so I'm not even sure if my hosts.allow entries are correct: upsd : ipaddressofclientgoeshere ups

All, I have successfully compiled and installed openssl 0.9.6g and am attempting to install openssh-3.4p1. I am using the following cofigure command for openssh: ./configure --prefix=/opt/local --sysconfdir=/opt/local/etc/ssh --with-tcp-wrappers --with-ssl-dir=/opt/local --with-rand-helper The configuration appears to work flawlessly. However, when I try to make the package I get the