Bug#335902: proftpd doesn't honor RFC959

Francesco Paolo Lovergine a écrit : On Wed, Oct 26, 2005 at 08:01:15PM +0200, Fabrice LORRAIN wrote: Correct, MaxInstance=Maxclient=1 in this testbed configuration. Our regular ftp server was running with MaxInstance=Maxclient=100. Set maxclient < maxinstance (or remove it at all), Setti

Bug#335902: proftpd doesn't honor RFC959

On Wed, Oct 26, 2005 at 08:01:15PM +0200, Fabrice LORRAIN wrote: > > Correct, MaxInstance=Maxclient=1 in this testbed configuration. > Our regular ftp server was running with MaxInstance=Maxclient=100. > Set maxclient < maxinstance (or remove it at all), that should cause a nice handling of lim

Bug#335902: proftpd doesn't honor RFC959

Francesco Paolo Lovergine a écrit : severity 335902 normal thanks Ack. 421 is non mandatory in RFC959. Btw, add your proftpd.conf and a dumping session to the report to help. proftpd.conf attached. By the way, any clue why with this conf proftpd still binds itself to all the interfaces ?

Bug#335902: proftpd doesn't honor RFC959

severity 335902 normal thanks 421 is non mandatory in RFC959. Btw, add your proftpd.conf and a dumping session to the report to help. Thanks Upstream reports: My guess is that they're encountering their MaxInstance limit, rather than MaxClient since that will cause proftpd to simply close the c

Bug#335902: proftpd doesn't honor RFC959

tags 335902 upstream forward [EMAIL PROTECTED] thanks On Wed, Oct 26, 2005 at 06:24:44PM +0200, Fabrice LORRAIN wrote: > Package: proftpd > Version: 1.2.10-15sarge1.0.1 > Severity: important > > > Hello, > > proftpd doesn't send error code 421 when there is no more session > allowed (from rfc9

Bug#335902: proftpd doesn't honor RFC959

Package: proftpd Version: 1.2.10-15sarge1.0.1 Severity: important Hello, proftpd doesn't send error code 421 when there is no more session allowed (from rfc959, section 4.2.1 "421 Service not available, closing control connection.") Instead, proftpd close the tcp session (FIN,ACK) from the serv