Skip to contentSkip to conversation

New: update vsftpd to 3.0.0

Buildroot bugzilla at busybox.net 1 participant 2 messages Jun 27, 2012 – Oct 16, 2012

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=5330

Summary: update vsftpd to 3.0.0
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: aras.vaichas at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0

The December 2011 vsftpd-2.3.5 release caused a few headaches for people.

http://www.benscobie.com/fixing-500-oops-vsftpd-refusing-to-run-with-writable-root-inside-chroot/

http://imbuzu.wordpress.com/2012/05/07/fixing-500-oops-vsftpd-refusing-to-run-with-writable-root-inside-chroot-on-vsftpd/

A "fix" was introduced in April 2012 with a release of vsftpd-3.0.0.

I have made a change to my copy (Buildroot-2012.05) and the vsftpd-2.3.4-dont-force-largefile.patch patch applies without any problems.

Do I submit a patch through this interface (Bugzilla)?

Sorry, it's been ages since I've submitted patches, can someone please send me a URL of the formal procedure, e.g. sign off, etc?

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 5330] update vsftpd to 3.0.0

https://bugs.busybox.net/show_bug.cgi?id=5330

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #1 from Peter Korsgaard <[email protected]> 2012-10-16 21:16:16 UTC --- Bumped in git by Gustavoz to 3.0.2. (75f6e1df60b29e)

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.