maxsem@mwlog1001:/srv/mw-log$ grep ListeriaBot archive/badpass.log-20170821 | wc -l 28036 maxsem@mwlog1001:/srv/mw-log$ grep ListeriaBot archive/badpass.log-20170821 | grep '"successful":true' | wc -l 28035
Is everything all right with it?
As of late June 2020, it's upto around 35000 a day
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Resolved | Urbanecm | T256533 Identify accounts with very high login rate | |||
| Resolved | Magnus | T173777 ListeriaBot logs in 35000 times a day |
It was written to do single edits, so it does log in before each one. I can try and change it if it's a problem?
You really ought to. Simply using a session cookie to retain the login data will save some major resources IMO.
With fixing all other bots, now 26% of all logins across all of cluster is ListeriaBot. If this continues, we will block the bot.