[SRU] Please backport vsftpd 3.0.2-1ubuntu1 (main) from raring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Precise Backports |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal Backports |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Please backport vsftpd 3.0.2-1ubuntu1 (main) from saucy to precise.
Reason for the backport:
=======
If you see the original software changelog: https:/
- Add stronger checks for the configuration error of running with a writeable
root directory inside a chroot(). This may bite people who carelessly turned
on chroot_local_user but such is life.
This provokes that if a writeable root for a chroot exists, it will fail to log in with this message:
500 OOPS: vsftpd: refusing to run with writable root inside chroot ()
If you look further in 3.0 version a key config for vsftpd.conf has been included that allows to set a writeable chroot:
500 OOPS: vsftpd: refusing to run with writable root inside chroot ()
This is the situation up to now in precise and quantal (raring and saucy already include this 3.0 version) in both i386 and amd64.
Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.
You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s saucy -d raring vsftpd
* raring:
[ ] Package builds without modification
[ ] vsftpd installs cleanly and runs
Reverse dependencies:
=======
The following reverse-
vsftpd
------
* ubumirror
[ ] raring (Reverse-Suggests)
* harden-servers
[ ] raring (Reverse-Conflicts)
Changed in quantal-backports: | |
status: | New → Incomplete |
Changed in precise-backports: | |
status: | New → Incomplete |
tags: | removed: precise |
Changed in quantal-backports: | |
status: | Confirmed → Won't Fix |
Changed in precise-backports: | |
status: | Confirmed → Won't Fix |
Have you tested that the backport builds and runs fine on precise and quantal?