On Mon 03/Nov/2014 19:48:55 +0100 I wrote:
For example, as I use MySQL, I could add a badpw field in the user table,
and
craft a select statement that returns the honeypot's username when the input
local_part matches the compromised password instead of the good one.
I cannot, of course.
Alessandro Vesely writes:
On Mon 03/Nov/2014 19:48:55 +0100 I wrote:
For example, as I use MySQL, I could add a badpw field in the user
table, and
craft a select statement that returns the honeypot's username when the
input
local_part matches the compromised password instead of the
On 07/11/14 21:52, Sam Varshavchik wrote:
Is it possible to add authmysql twice (and have them behave differently)?
Nope. You could list authmysql twice, but each instance uses the same config
file.
Maybe falling over to different auth backends might work but, Sam, it would
be really neat to
Mark Constable writes:
On 07/11/14 21:52, Sam Varshavchik wrote:
Is it possible to add authmysql twice (and have them behave differently)?
Nope. You could list authmysql twice, but each instance uses the same
config
file.
Maybe falling over to different auth backends might work but,
Hi,
a mailbox of mines was compromised last week. I hate that. I changed the
password just before the automated limit blocked the account. The spammer
seems to have a huge botnet, and I still see 535 Authentication failed in the
logs. I set DEBUG_LOGIN=2 to make sure they are using the old
