>> hi, may you try this patch in attachment?
Hi! Sorry for the late reply, didn't get any mail..
>>to apply, save the attachment in /tmp and as root,
>>$ cd /usr/share/pyshared/freevo
>>$ patch -p1 < /tmp/cdrom.patch
Yes! It works!!
Thanks a lot for your work, Andrea. I've been investigating th
Bug persists on freevo 1.9.0-1. Furthermore, the behaviour described by
Darkhorse is just the same on my machine when mplayer is the default player.
When you use xine, selecting a video file (regardless the size) just takes you
back to the upper directory on the cd/dvd. The line on the logs is j
On Fri, 22 Dec 2006 14:05:21 -0500
Yaroslav Halchenko <[EMAIL PROTECTED]> wrote:
> ok - everything is fixed now
>
> by default we would use /var/log/vsftpd.log and regexp matches both
> vsftpd and auth.log entries if logpath gets changed over to auth.log ;)
> (I fixed it and checked myself now,
On Thu, 21 Dec 2006 23:58:37 -0500
Yaroslav Halchenko <[EMAIL PROTECTED]> wrote:
> Hi
>
> It seems that Debian shipped vsftp comes with pam support which gets
> enabled if you enable local_enable option
It comes with pam support for local users (sorry I didn't express myself
correctly) but not
On Thu, 21 Dec 2006 22:09:05 -0500
Yaroslav Halchenko <[EMAIL PROTECTED]> wrote:
> > Hi again
> > Yes, it works! But it needed changing my jail.local also; that solved the
> > problem. Debian etch version didn't
> > work even changing jail.local. Keep reading.
> etch version doesn't have right f
On Thu, 21 Dec 2006 11:59:38 -0500
Yaroslav Halchenko <[EMAIL PROTECTED]> wrote:
> You can also read my blurb below - ie how I came to the fact that the
> fact that upstream started to ship vsftpd section (versions 0.6.2 and
> 0.7.1) which were different from my previously Debian shipped,
> and it
On Thu, 21 Dec 2006 09:14:08 -0500
Yaroslav Halchenko <[EMAIL PROTECTED]> wrote:
> Hi Antonio,
>
> Send me
> 1. output of commands
> fail2ban-client status
> fail2ban-client status vsftpd
Hi Yaroslav
1) [EMAIL PROTECTED]:/# fail2ban-client status
Status
|- Number of jail: 2
`- Jail list:
Package: fail2ban
Version: 0.7.5-2
Severity: important
Since the upgrade to 0.7, fail2ban does not ban vsftpd erroneous logins. The
severity I've chosen is important because ssh bad login attempts are correctly
stopped by fail2ban, so it is not critical.
As stated in /etc/fail2ban/jail.conf, I c
Subject: gnump3d: "401 OK"- No connection to server
Package: gnump3d
Version: 2.9.9.9-1
Severity: important
*** Please type your report below this line ***
After upgrading gnump3d to 2.9.9.9-1, I get a "401 OK" (no connection to
server), even with a successful login. If I remove the "password
prot
Subject: fail2ban: Fail2ban fails to ban vsftpd logins
Package: fail2ban
Version: 0.6.1-1
Severity: normal
*** Please type your report below this line ***
Fail2ban fails to ban vsftpd incorrect logins. Depending on the configuration,
I get the following:
1) Configuration 1
failregex = FAIL LOGI
10 matches
Mail list logo
