popa3d-users - Re: Log / Client IP Address

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / community lists wiki CVSweb mirrors signatures
bringing security into open environments

Order Openwall GNU/*/Linux 2.0 on a CD with delivery worldwide

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Sat, 5 Apr 2003 02:46:03 +0400
From: Solar Designer <solar@...nwall.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: Log / Client IP Address

On Thu, Apr 03, 2003 at 12:51:22PM +0100, Daniel Leite wrote:
> 	if you are running popa3d as a standalone server, its the popa3d
> 	server that does the IP logging,

Yes.

> so you have to enable it there

No, by your very choice of standalone mode you indicate that you have
no other software which would do that logging so popa3d knows it
should do it.  There's no additional configuration necessary.

> 	if you are using the inetd service (or xinetd), then its the inetd
> 	that do the IP login and then you must search how to enable the 
> 	logging in your super daemon
> 	(in other words, you can rule out the popa3d and the syslogd as 
> 	the source of the problem, stick around with inetd until it starts
> 	to log things)

That's right.

-- 
/sd