Bonjour à tous,

Depuis la mise-à-jour vers Debian 5 (stable), les logs de proftpd sont
en anglais :

fÃ(c)v 18 22:08:37 neptune proftpd[29656] neptune.milkyway
(MACHINTRUC[XX.XX.XX.XX]): USER XXXX: Login successful.

Du coup, la date n'est plus reconnu par fail2ban:

r...@neptune:/var/log# fail2ban-regex proftpd/proftpd.log
"\(\S+\[<HOST>\]\)[: -]+ USER \S+ \(Login failed\): Incorrect
password\.$"

Running tests
=============

Use regex line : \(\S+\[<HOST>\]\)[: -]+ USER \S+ \(Login failed\):...
Use log file   : proftpd/proftpd.log

Found a match for ' neptune proftpd[29758] neptune.milkyway
(MACHINTRUC[XX.XX.XX.XX]): USER XXXX(Login failed): Incorrect
password.
' but no valid date/time found for 'fÃ(c)v 18 22:28:09'. Please
contact the author in order to get support for this format
Found a match for ' neptune proftpd[29759] neptune.milkyway
(MACHINTRUC[XX.XX.XX.XX]): USER XXXX(Login failed): Incorrect
password.
' but no valid date/time found for 'fÃ(c)v 18 22:28:21'. Please
contact the author in order to get support for this format
Found a match for ' neptune proftpd[29760] neptune.milkyway
(MACHINTRUC[XX.XX.XX.XX]): USER XXXX(Login failed): Incorrect
password.
' but no valid date/time found for 'fÃ(c)v 18 22:28:34'. Please
contact the author in order to get support for this format

Results
=======

Failregex
|- Regular expressions:
|  [1] \(\S+\[<HOST>\]\)[: -]+ USER \S+ \(Login failed\): Incorrect password\.$
|
`- Number of matches:
   [1] 0 match(es)

Ignoreregex
|- Regular expressions:
|
`- Number of matches:

Summary
=======

Sorry, no match

Look at the above section 'Running tests' which could contain important
information.


Savez-vous comment corriger le problème ?

Merci d'avance.

R.O.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/DebFrFrenchLists
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs "From" et
"Reply-To:"

To UNSUBSCRIBE, email to debian-user-french-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Répondre à