On Sat, Nov 29, 2014 at 4:36 PM, Yaroslav Halchenko <y...@debian.org> wrote:
> On Sat, 29 Nov 2014, László Böszörményi (GCS) wrote:
>> May you give me some details how it happened in Sid?
>
> ok -- I will try to replicate again under sid (trickier since I have no sid on
> publicly bombarded servers)
You may also backport the recent, SQLite3 3.8.7.2-1 upload to your box.
>> > unfortunately we haven't logged the sql queries so not sure on exact one,
>> > but I
>> > think it was this one, which if executed from the shell seems to not cause
>> > the
>> > segfault...
>
>> > n {1..100}; do sqlite3 -list fail2ban.sqlite3 'SELECT ip, timeofban, data
>> > FROM bans WHERE 1 AND jail="sshd" AND ip="111.74.239.35" ORDER BY ip,
>> > timeofban' >/dev/null && echo success; done
You may try the same loop with a Python script doing the same SQLite3 query.
> FWIW -- I am the Fail2ban maintainer... but fail2ban is just a 'trigger'
> here -- it is a purely Python implementation so either it is sqlite3 or python
> bindings which are at fault here
Then I do wonder why do you use an unofficial fail2ban backport
instead of doing it yourself.
Cheers,
Laszlo/GCS
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
