On 07.09.2011 12:16, Alex Bligh wrote:
> The released resolution broke a production environment here: See #844185
>
> I propose this is instead fixed by disabling it in vsftpd.
>
The problem is that nobody can say that vsftp was or is the only vector that
allows to DOS a system doing something th
On 02/06/11 14:32, Rachel Greenham wrote:
> On 01/06/11 17:08, Stefan Metzmacher wrote:
>> Fixing vsftpd looks like a much better fix for this
Also presumably disabling it in vsftpd will hurt people who want to use
that in an lxc setting without providing an easily-applied solution.
--
Rachel
On 01/06/11 17:08, Stefan Metzmacher wrote:
> Fixing vsftpd looks like a much better fix for this
It would seem at first sight to be simpler; but presumably the problem
was that there are bugs in the implementation in the Lucid kernel (and
upstream) that won't necessarily *only* impact vsftpd us
Excerpts from Rachel Greenham's message of Sat Apr 16 11:25:10 UTC 2011:
> I think I've been experiencing this bug on a production vmware guest
> server running Lucid with vsftp being connected to frequently by client
> machines.
>
> The thing is, this bug shows as being "fix committed" - and the
