1 message in net.sourceforge.lists.courier-users[courier-users] Courier-imap and tcpw...
FromSent OnAttachments
Andrey V. MalyshevOct 10, 2006 7:39 pm.tgz
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Courier-imap and tcpwrapperActions...
From:Andrey V. Malyshev (am@krasn.ru)
Date:Oct 10, 2006 7:39:31 pm
List:net.sourceforge.lists.courier-users
Attachments:
patch-tcpwrap.tgz - 5k

Hello!

I have wrote simple patch for couriertcpd to use tcp wrapper call (libwrap, hosts_ctl() call and /etc/hosts.allow). I know about "access" feature of couriertcpd but I'd like to use more common method for connection controlling.

How it works: if tcp wrapper enabled, then remote client is checked there before "access" check. If libwrap returns "deny", connection is denyed, else continuing with "access" etc.

The patch is applicable both for cvs version (patch-tcpwrap::configure-in + patch-tcpwrap::tcpd) and for end-user distributive, for example, in FreeBSD ports (patch-tcpwrap::configure + patch-tcpwrap::tcpd), for version 4.1.1. By default tcpwrapper is enabled, it is tuned by --without-libwrap or --with-libwrap at configure stage.

Tested on FreeBSD 6.1.

I hope it is possible to merge this patch (corrected as it needed). More features is better than less ones, I think :-)

Thanks for attention.