From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5330] New: update vsftpd to 3.0.0
Date: Wed, 27 Jun 2012 08:36:39 +0000 (UTC) [thread overview]
Message-ID: <bug-5330-163@https.bugs.busybox.net/> (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?
--
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.
next reply other threads:[~2012-06-27 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 8:36 bugzilla at busybox.net [this message]
2012-10-16 21:16 ` [Buildroot] [Bug 5330] update vsftpd to 3.0.0 bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-5330-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.