proftpd - mod_vroot failing
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| proftpd-mod-vroot (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When mod_vroot is enabled, it does not work as it would have in Ubuntu 12.04/12.10. DefaultRoot seems to be ignored, and it chdirs to system's root (/) rather than user's home directory. Fortunately, anonymous access fails completely.
I'm not an expert with pro-ftpd or this module, but I can tell behavior has changed since switching to raring, and I can't seem to get it to work again despite trying to follow the manpage
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: proftpd-mod-vroot 0.9.2-2build1
Uname: Linux 3.9.0-030900rc8
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Mon Apr 29 14:43:04 2013
InstallationDate: Installed on 2010-12-11 (870 days ago)
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_ZA.UTF-8
SHELL=/bin/bash
SourcePackage: proftpd-mod-vroot
UpgradeStatus: Upgraded to raring on 2013-04-26 (3 days ago)
| Dimitri Pappas (fragtion) wrote | #1 |
| information type: | Private Security → Public |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in proftpd-mod-vroot (Ubuntu): | |
| status: | New → Confirmed |
Status changed to 'Confirmed' because the bug affects multiple users.