gmane.mail.popa3d.user

popa3d 1.0

Hi,

For those few on the announcement list who don't know this yet, popa3d
is a tiny POP3 daemon which attempts to be extremely secure, reliable,
RFC compliant, and fast (in that order).  Now, to the news:

I've released popa3d 1.0.  This means that I consider popa3d to be
mature enough to enter its 1.x era.

The changes since version 0.6.4.1 released almost a year ago are
minimal.  This means that the code has been well tested and no new
bugs are introduced with this minor update (or at least I hope so).

popa3d is available off its homepage at:

	http://www.openwall.com/popa3d/

As usual, there're detached PGP signatures for the tarballs.

The change log is available at:

	http://www.openwall.com/popa3d/CHANGES.shtml

--

-- 
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598  fp: 6429 0D7E F130 C13E C929  6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments

headers

Sean Kelly | 1 Jun 08:25

RE: popa3d 1.0

Hi,

I was wondering if anyone could help me produce a patch using diff (or
what?) - I made a couple quick and simple code changes that will add the
IP address of the connected user in parenthesis on the log line after
authentication. It's only a couple lines of code and produces the
following output in the logs:

May 31 22:28:47 localhost popa3d[21547]: Authentication passed for
dkelly\ (69.107.106.62)
May 31 22:31:47 localhost popa3d[21562]: Authentication passed for
skelly\ (69.107.106.62)

Anyway, I've never made nor used any kind of source code patch before
and have no idea how to do it, but would like to switch to the 1.0 code
and I think this would be a nice little patch release that is simple and
succinct. I made the changes to the 0.6.4.1 code-base.

Of course there are plenty of uses for recording the IP address in this
manner, but personally I want to use it as IP-based authentication for
pop-before-send. The other approaches seemed too involved or tricky to
me and I wanted a much simpler mechanism. With this, all I will do is
use a perl script to monitor the incoming log statements from popa3d and
add IP's to the SMTP access file, and remove them after some expiration
period.

Well I'd appreciate it if someone wouldn't mind lending a hand. I'll be
happy to host the patch distribution afterward.

Thanks,

(Continue reading)

headers

Mr Duck | 1 Jun 15:04

Re: popa3d 1.0

> I was wondering if anyone could help me produce a patch using diff (or
> what?) - I made a couple quick and simple code changes that will add the
> IP address of the connected user in parenthesis on the log line after
> authentication.

   Would you mind posting the URL for d/l of this patch once you've 
completed it. I'd love to use it as well. (=  Thanks!!

TLD/Brad

headers

Solar Designer | 2 Jun 06:04

Re: popa3d 1.0

Hi Sean,

On Tue, May 31, 2005 at 11:25:10PM -0700, Sean Kelly wrote:
> I was wondering if anyone could help me produce a patch using diff (or
> what?) -

Are you asking for help on using the diff program?  If so, "man diff"
and "info diff" should have it.  In short, the command you'd use is
probably like this:

diff -urpN popa3d-1.0.orig popa3d-1.0 > popa3d-1.0-whatever-1.diff

where popa3d-1.0.orig is the original popa3d 1.0 tree, and popa3d-1.0
is your modified version.  Be sure to remove any extra files before
you run this (run "make clean" or so), and also not include any local
changes (such as those to params.h) in the patch file you distribute.

> I made a couple quick and simple code changes that will add the
> IP address of the connected user in parenthesis on the log line after
> authentication.

I'm not sure why you did it given that some of the patches already in
contrib do the same.  OK, I understand that it may be quicker to add
the few lines to do it rather than to download and apply a patch.  And
those other patches do more than just that.

--

-- 
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598  fp: 6429 0D7E F130 C13E C929  6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments

(Continue reading)