9 Apr
2013
9 Apr
'13
12:22 a.m.
I put it in debug mode but then it logs all of the passwords good and
bad. I am not interested in having the good passwords in the log
files. I downloaded the sources for 1.18 and compiled them. That seemed
to work like the version I am running. While it did seem to work fine
it was logging errors like this:
Apr 8 17:05:23 mailproxy1 perdition[9330]: Connect:
192.168.0.50->192.168.0.100
Apr 8 17:05:23 mailproxy1 perdition[9330]: Fatal error establishing SSL
connection to client
Even with this error it was working even with ssl. I would really
rather run the newer version since it give a little more detail in the
ps and the logs. I would also rather install from rpm instead of
compiling so any updates would be much easier. The rpm also comes with
a nice startup script and easy config via /etc/sysconfig/perdition.
Does anyone know how to get the log_passwd to work in 1.19-rc5?
On 04/06/2013 12:23 PM, Mark Hamilton wrote:
I have been using an older version of perdition for a
while now with no
issues. I am going to be upgrading the server running the proxy. I
installed a clean Centos 6.4 on a new machine. I put in the repo for
perdition and installed it. After a couple of config file tweaks to add
mysql, ssl etc I launced it and it worked fine right out of the shoots.
My problem is we use the log_passwd fail to help our users when they are
messing up their password. It has worked great on the older version of
perdition. On this version we don't seem to get the bad password logged
even with log_passwd fail in the config file. I am sure I am just
missing something somewhere. Is it logged to a different log level or
something like that?
Current version: Logging failed password fine
Perdition = 1.17
OS = Slackware 9.1.0
New version: Not logging failed passwords
Perdition = 1.19-rc5
OS = Centos 6.4
Thanks for any help.
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users