Date: Fri, 31 May 2002 20:39:33 +0400 From: Solar Designer <solar@openwall.com> To: Zaitsev Serg <root@aprcity.ru> Cc: dinoex@FreeBSD.org, ports@FreeBSD.org Subject: Re: popa3d-0.5.1 Message-ID: <20020531203933.A29186@openwall.com> In-Reply-To: <02d701c208a4$ef574d50$250010ac@aprcity.com>; from root@aprcity.ru on Fri, May 31, 2002 at 05:13:16PM %2B0400 References: <02d701c208a4$ef574d50$250010ac@aprcity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 31, 2002 at 05:13:16PM +0400, Zaitsev Serg wrote: [ I am CC'ing ports@ on this reply, although this discussion actually has very little to do with FreeBSD ports. This is just to let others know that this is being handled. Please drop the ports@ on any further replies, thanks! ] > Dear dinoex@FreeBSD.org . > On http://www.freebsd.org/ports/mail.html you pointed as maintainer secure > POP3 server popa3d-0.5.1. > I allready have fully working POP3 server cucipop. It is good. But it has no > support SSL tunneling and I unrest for probability to catch plain text > accounts and passwords from traffic. I have find out only one secure POP3 > server from lot ones on http://www.freebsd.org/ports/mail.html. > I had compile popa3d-0.5.1 on FreeBSD 4.4. POP3 is OK, POP3S do not. popa3d doesn't yet have built-in SSL support. You're supposed to use it with stunnel to get pop3s working. You also need to generate a certificate. There're HOWTO's explaining the steps, please search around. (There's nothing specific to popa3d in that.) Built-in SSL support for popa3d is planned. > su root > fetch http://www.openssl.org/source/openssl-0.9.6d.tar.gz > > Do you know what is difference with > http://www.openssl.org/source/openssl-engine-0.9.6d.tar.gz ? That is explained on their web site. > tar zxf openssl-0.9.6d.tar.gz > cd openssl-0.9.6d > ./config > make > make test > make install I don't think you needed to do all that, FreeBSD includes OpenSSL in base tree. > fetch http://www.openwall.com/popa3d/popa3d-0.5.1.tar.gz > tar zxf popa3d-0.5.1.tar.gz > cd popa3d-0.5.1 > cat INSTALL What does this have to do with FreeBSD ports, then? You install popa3d manually and could have mailed just me, the author. > /usr/bin/ee Makefile > #CFLAGS += -DHAVE_OPENSSL > #LIBS += -lcrypt > #LIBS += -lcrypto > change to > CFLAGS += -DHAVE_OPENSSL > LIBS += -lcrypt > LIBS += -lcrypto That isn't SSL support. popa3d is merely able to use the implementation of MD5 found in OpenSSL's crypto library, instead of the one I did myself and am including with popa3d sources (under md5/). > chown popa3d:popa3d /var/empty That's _very_ wrong. The comment in params.h where you define that directory explicitly says to _not_ do a thing like that. > kill -HUP `cat /var/run/inetd.conf` Huh? ;-) -- /sd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020531203933.A29186>